iOS build fail

Description
It appears to be related to the swift code, I have pasted the related Fastlane logs below.
Version
v2.9.5
What platforms are you seeing the problem on?
iOS
System info
› Compiling react-native-adapty Pods/react-native-adapty-sdk » react-native-adapty-sdk-dummy.m
› Compiling react-native-adapty Pods/react-native-adapty-sdk » RNAdapty.m
› Compiling react-native-adapty Pods/react-native-adapty-sdk » RNAContext.swift
› Compiling react-native-adapty Pods/react-native-adapty-sdk » RNAdapty.swift
› Compiling react-native-adapty Pods/react-native-adapty-sdk » RNAParamMap.swift

❌  (node_modules/react-native-adapty/lib/ios/RNAParamMap.swift:33:20)

  31 |         let jsonString: String = try getRequiredValue(for: key)
  32 |
> 33 |         return try getDecodedValue<T>(for: key, jsonString: jsonString, jsonDecoder: jsonDecoder)
     |                    ^ cannot specialize a non-generic definition
  34 |     }
  35 |
  36 |     public func getDecodedOptionalValue<T: Decodable>(for key: ParamKey, jsonDecoder: JSONDecoder) throws -> T? {

❌  (node_modules/react-native-adapty/lib/ios/RNAParamMap.swift:39:20)

  37 |         guard let jsonString: String = getOptionalValue(for: key) else { return nil }
  38 |
> 39 |         return try getDecodedValue<T>(for: key, jsonString: jsonString, jsonDecoder: jsonDecoder)
     |                    ^ cannot specialize a non-generic definition
  40 |     }
  41 |
  42 |     func getDecodedValue<T: Decodable>(for key: ParamKey, jsonString: String, jsonDecoder: JSONDecoder) throws -> T {
› Compiling react-native-adapty Pods/react-native-adapty-sdk » RNABridgeError.swift
› Compiling react-native-adapty Pods/react-native-adapty-sdk » RNAConstants.swift
⚠  Script has ambiguous dependencies causing it to run on every build.
   To fix, go to: Xcode » Sarmiza/Sarmiza » Build Phases » 'Start Packager'
   Either: Uncheck "Based on dependency analysis", or select output files to trigger the script
⚠  Script has ambiguous dependencies causing it to run on every build.
   To fix, go to: Xcode » Sarmiza/Sarmiza » Build Phases » 'Bundle React Native code and images'
   Either: Uncheck "Based on dependency analysis", or select output files to trigger the script
▸ ** ARCHIVE FAILED **
▸ The following build commands failed:
▸ 	SwiftCompile normal arm64 Compiling\ RNAParamMap.swift /Users/expo/workingdir/build/node_modules/react-native-adapty/lib/ios/RNAParamMap.swift (in target 'react-native-adapty-sdk' from project 'Pods')
▸ 	CompileSwift normal arm64 /Users/expo/workingdir/build/node_modules/react-native-adapty/lib/ios/RNAParamMap.swift (in target 'react-native-adapty-sdk' from project 'Pods')
▸ (2 failures)
** ARCHIVE FAILED **
The following build commands failed:
	SwiftCompile normal arm64 Compiling\ RNAParamMap.swift /Users/expo/workingdir/build/node_modules/react-native-adapty/lib/ios/RNAParamMap.swift (in target 'react-native-adapty-sdk' from project 'Pods')
	CompileSwift normal arm64 /Users/expo/workingdir/build/node_modules/react-native-adapty/lib/ios/RNAParamMap.swift (in target 'react-native-adapty-sdk' from project 'Pods')
(2 failures)

Exit status: 65
+-------------+-------------------------+
|           Build environment           |
+-------------+-------------------------+
| xcode_path  | /Applications/Xcode.app |
| gym_version | 2.211.0                 |
| sdk         | iPhoneOS16.2.sdk        |
+-------------+-------------------------+

@elsa17z, thank you for the report! What's your Xcode version? And could you also please update to v2.9.6?

same problem
XCode 14.2
react-native-adapty 2.9.6

In my case only version 2.9.2 worked.
Apparently, the error is due to these changes in version 2.9.3 -
https://github.com/adaptyteam/AdaptySDK-React-Native/commit/7669a626e4c3a4d54b0e6bb15356b9113882b599#diff-7d0f436e4523a6f4896c1f7ed142564a2a49f6d89112847f136505987d24dcc3

@evgenijchul thank you for the report! We'll debug it on Xcode 14.2

@elsa17z @evgenijchul could you please try v2.9.7?

"react-native-adapty": "^2.9.7"
The build is ok and I don't see any issues with the package working in the app. Thanks. 👍


[$250] [Dev][StrictMode] Popover menu has no background smallscreen

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?:  DEV only
Reproducible in production?: DEV only
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @ishpaul777
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1720819445275459
Action Performed:
Long press on any report in LHN
Expected Result:
Popover menus haves translucent background
Actual Result:
Popover menu dont have background
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[x] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/894fc80a-baf9-4aac-b71f-43c212d380a5

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ff564d543a9355a6
Upwork Job ID:<PHONE_NUMBER>309666872
Last Price Increase: 2024-07-15

Issue OwnerCurrent Issue Owner: @allroundexperts

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

I'm not able to test since I don't work in a DEV environment. @allroundexperts could you try reproducing this?

It's easily reproducible @lschurr.
https://github.com/user-attachments/assets/d6b6fc22-991d-428a-97f7-43d1eda4708b

Proposal
Please re-state the problem that we are trying to solve in this issue.
Popover menu has no background in small screens in the development environment when using the strict mode.
What is the root cause of that problem?
ReactNativeModal isn't showing the backdrop background and the opacity of the background is set to zero when the strict mode is enabled. The background appears as expected if the strict mode is disabled.
What changes do you think we should make in order to solve the problem?

Using the ReactNativeModal ref, we can set the opacity to the desired value so the background appears as expected by adding the following code snippet:
const modalRef = useRef(null);
try{
    modalRef.current.backdropRef.ref.style.opacity = !shouldUseCustomBackdrop && hideBackdrop ? 0 : variables.overlayOpacity;
}
catch {}

in line 209 at: https://github.com/Expensify/App/blob/105dce5151053bf6c81e60e68a610dd888c5da45/src/components/Modal/BaseModal.tsx#L205-L218
then bind the ref to the ReactNativeModal at line 224 in the following code snippet:
https://github.com/Expensify/App/blob/105dce5151053bf6c81e60e68a610dd888c5da45/src/components/Modal/BaseModal.tsx#L220-L230
Below is a screenshot after applying the change:

What alternative solutions did you explore? (Optional)
The last commit to the React Native Modal library used in the Popover menu is 2 years old and is looking for maintainers, which is mentioned in https://github.com/react-native-modal/react-native-modal?tab=readme-ov-file#announcements, so we can use the React Native built-in Modal component or any other wrapper library that is compatible with the strict mode and maintained.

Thanks for the proposal @dominictb. Your RCA seems to be accurate, but I'm not sure if patching / editing the package is the correct way to proceed here. Software mansion maintains the react-native-reanimated library, and I think it would be great if we can consult about this with them in the open source channel. Can you spin up a message and tag me? Thanks!

@isogit123 Your RCA is incomplete. Please make sure to include proper root cause in order for the proposal to be accepted.

Proposal updated

Any update on this one @allroundexperts?

@allroundexperts sorry but I think we are referring to 2 different libraries here. The package mentioned in my proposal is react-native-animatable, not react-native-reanimated. I don't think we maintain the react-native-animatable right?

Yes, my bad. Thinking about it now, can we just use react-native-reanimated only here?

Bump on this @allroundexperts

@dominictb Do we have any existing patches in our codebase for this library?

Okay. Can we somehow not use react-native-animatable in our codebase and just use react-native-reanimated instead?

We still need to patch react-native-animatable to fix the second issue mentioned here: #45385 (comment)

Ah, I see. I guess that's the best option then.

@dominictb's proposal looks good to me. Let's create a patch for the package.
🎀 👀 🎀 C+ reviewed

Any update @dominictb?

Could you please review the PR @allroundexperts ?

Reviewed!

@dominictb Any update here on your new PR? @lschurr This is still not fixed.

Ok, noted

@dominictb any update here?

Thanks, I have removed you and we are back to looking for proposals here.

Removing Al since I'm back to work - @allroundexperts - is this still broken? Are we waiting on new proposals?

Bump on this one @allroundexperts - can you confirm this is bug is still happening?

Thank you! Going to close this one.

@lschurr I reviewed a PR here that caused a regression. Can I get a payment summary, please?


Implement Air Movement Limits

As a Game Designer,
I want to limit special movements of the player,
So that the player makes more interesting decisions in the game.
Limits limit the number of uses of certain movements, and can recharge by waiting or collecting items.
Movements include swing, dash, and zipToPoint

added


yolov4 quantize float16

is it important to quantize yolo4 into either float16 or int8 ?
what is the difference between them ?
and when I run the command ( python convert_tflite.py --weights ./checkpoints/yolov4-416 --output ./checkpoints/yolov4-416-fp16.tflite --quantize_mode float16 ) I got this error :
OSError: SavedModel file does not exist at: ./checkpoints/yolov4-416/{saved_model.pbtxt|saved_model.pb}

You don't necessarily have to quantize the model. It just makes the inference faster. To understand the difference, see tensorflow post-training quantization doc
Model doesn't exist error is due to the path that you are giving don't contain saved_model.pb, which is generated by python save_model.py --weights ./data/yolov4.weights --output ./checkpoints/yolov4-416 --input_size 416 --model yolov4 --framework tflite


Question 119 Incorrect Answer Description

The end of the answer's description says:

member.getLastName?.(): member is not defined: member.getLastName() is nullish. The expression returns undefined.

In reality, like the B says, it throws a ReferenceError and does not return undefined. It also doesn't explain why it returns ReferenceError.

Too many similar questions


Add documentation for huggingface recipes

What does this PR do? Please describe:
This PR includes some documentation for the huggingface recipes
Does your PR introduce any breaking changes? If yes, please list them:
None
Check list:

[X] Was the content of this PR discussed and approved via a GitHub issue? (no need for typos or documentation improvements)
[X] Did you read the contributor guideline?
[x] Did you make sure that your PR does only one thing instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests?
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (no need for typos, documentation, or minor internal changes)

Will close this PR as it was based on the whisper integration PR which included commits that shouldn't be in that PR. Sorry about that


Fix small UI issues in tracing ui

Summary

Minor improvements to the tracing UI
Checklist

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

@homanp, thank you for the pull request! I have reviewed the code diff and have a suggestion for improvement.
In the chat.tsx file, there is a change in the CardHeader component. The div element inside it has a class name of "flex justify-between space-x-4". I recommend modifying it to "flex items-start justify-between space-x-4" to align the content properly.
Here's the updated code snippet:

{run.inputs.input}

      {run.total_tokens} tokens

Please let me know if you have any questions or need further assistance. Keep up the great work!
--
Note: This comment was generated automatically by Superagent Code Reviewer 🥷


coreinit allocator functions

These functions are needed for GX2Perf initialization.

Can you create a doxygen group for the file and add it to the coreinit group?

Can you rename the header to memallocator.h and adjust the doxygen block? Just to be consistent with the other MEM* headers and decaf-emu.

Thanks!


Tag for 0.5

https://github.com/JuliaDB/JDBC.jl/pull/20 says it's needed.
I'm not sure if 0.5 is already done with:
https://github.com/aviks/JavaCall.jl/commit/66af85a69c43af18a784313a5f41ebb4925b393c
as I see tests failing. Is that a false alarm since there is no tag? I'm just new to this, and can't see the test [that are failing]..

JavaCall v0.4.0 tagged with julia 0.5 support


Possibly incorrect implementations of leading_ones and leading_zeros

From BitSlice (leading_zeros is symmetric),
pub fn leading_ones(&self) -> usize {
	self.first_zero().unwrap_or_default()
}

This function fails the test assert_eq!(bits![1, 1, 1].leading_ones(), 3);, which is not listed in the doc comment. Is this behavior intentional? If not, an implementation such as
pub fn leading_ones(&self) -> usize {
	self.first_zero().unwrap_or_else(|| self.len())
}

would fix it (though may or may not be the most efficient). If the behavior is intentional, it may be surprising to some users, and could stand to be documented.
Thanks for reading.

This was reported and fixed in #120 but I don't think I've published it to any of the released series. I apologize.

Ah no, my apologies--I should have taken a look at the closed issues. Thanks for the reply!


Suggestions on potential improvements

Great work here, really like this webpart, esp. the sticky part. I've tested it with some internal users and I have som feedback on suggested improvements:

Make the headings expandable/collapsible.

For lengthy, long scrolling pages it would make sense if it was possible to expand and collapse the headings under level 1 to give a better overvoew and visibly show the user at which point on the page they are at.

UX
The underscore for a mouseover is nice, but slightly lackluster, would it be possible to enahnce it more, perhaps a staying effect on the last item clicked? Also the stylechange on the bullets where not something that the users liked, they would rather see them being consistent or not at all.

Placing of "Return ot previous page"
Iit is good that one can chose to toggle on and off certain features, like the return to next page, but what would make it even better is if the user could decide if it should be at the top or the bottom of the TOC, preferrable above the title.  Perhaps just duplicating the feature and make the user able to have it both at the top and the bottom if they wish? Would exp. cater to the really lengthy TOCs where the user either has scrolled all the way to the bottom, or just instantly wants to go back.

Hi,
Thanks for the feedback. In all honesty, I probably won’t have time to look at this request in the near future, but here are some comments on the feedback.

A nice idea, but probably a good amount of work, so I’m not sure if this will ever happen.

I might look at this. With regards to the bullet styles, they actually use the SharePoint CSS to follow the site, but it should be possible to put in an override that could be toggled on/off.

This should be possible without too much work.

Of course, if anyone wants to do the work and put in a pull request, I’m more that happy to take a look at including the changes.

Hi @RedEchidnaUK ,
as MS recently updated the Text WebPart on a modern page and excluded Heading 1, now toc should include heading 4 for that matter.
How easy would it be possible to update this by pushing all headings one level up?
Where heading 2 in webpart would be a heading 1 in toc
heading 3 in text webpart would be a heading 2 in toc
and heading 4 would be heading 3 in toc.
Probably I'm going to take a look at it myself as well :)
Thank you.

Hi @oxygenson
The code already uses Heading 2 etc. and always has done. The change MS made was purely a graphical one as it's always been Heading 2 etc. behind the scenes in the HTML. I suppose the ToC configuration options should really say 'Heading 2' etc. rather than 'Heading 1' to avoid confusion, or perhaps it should just say 'Contents level 1' etc. for when MS change everything in the future.

Hi @RedEchidnaUK ,
Thank you for confirmation!
This issue was reported to me through a user when H1 disappeared. After a detailed check with them and your solution, I came to the same conclusion you explained, all works fine. Too bad only SP page doesn't have additional headings, three levels only is a bit harsh when writing documentation.
Thank you and appreciate your solution, especially the sticky feature.

@Dahnic I know it's been a long time since you requested some changes, but I have now implemented some of your requests in the latest version; the ability to change the list icons (including hide them) and the ability to choose where the 'Return to previous page' link is shown. Unfortunately, the other requests would require significant work and I just don't have the time at the moment.


Add handy market links.

Add market links.

Thanks! I just put the big three there. Which is Blockmodo, CoinMarketCap, and to a lesser degree I guess, Cryptocompare. I also added the registry file because a lot of devs use it to show data about EOS.
Anyway, thanks for putting this together. This is great!


NullReferenceException in iOS (related to BigTed)

Having this issue in iOS with Xamarin.Forms 2 project:

Please send the full stack trace as text.  It has cut off most of what I'm looking for.  Please also review FAQ #1 in the readme

Allan, it's related to #4, as i use a LaunchScreen. If i move the Loading to OnAppearing(), it works. How to show a loading wheel on the first page on XF?

Solved. I moved my Loading call to OnAppearing on my home page and to avoid to be called when back button is pressed, i added IsLoaded bool. Thanks


Sync Salesforce data using Airbyte

User Story

Setup Salesforce as a data source and the data lake as its destination in Airbyte.
Description/Context

[ ] Account with admin privileges in Salesforce to setup a [connected app](https://medium.com/@bpmmendis94/obtain-access-refresh-tokens-from-salesforce-rest-api-a324fe4ccd9b)
[ ] Configure the source in Airbyte using the credentials from the connected app

[ ] QA
[ ] Production

[ ] Test sync and verify that data is coming through

Acceptance Criteria

[ ]
Salesforce data is in the data lake.

Ran into a blocker when trying to set this up whereby the Salesforce account provided to us didn't have the required permissions to create a connected app.

@blarghmatey what did you do on this to make it work? Can this be closed?

The Describe table seems to have been the one that caused the failure that we were experiencing. I disabled that in the sync and it was able to complete, so we can close this issue now.


failed to sync service when sync helm failed with k8s

In GitLab by @liyanq528 on Sep 18, 2019, 18:02

In GitLab by @luotian-github on Nov 8, 2019, 08:06
fixing by weiting

In GitLab by @sokril on Nov 8, 2019, 08:06
fixed by#2205

In GitLab by @sokril on Nov 8, 2019, 08:34
assigned to @sokril

In GitLab by @liyanq528 on Dec 3, 2019, 01:42
closed


system-path: Remove defaultPackages option

Description of changes
None of these tools are necessary for a minimal system.
Closes #263289.
@ofborg test disable-installer-tools
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) nix-build --attr nixosTests.disable-installer-tools
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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[x] (Module updates) ~Added~ Modified a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg test installer installer-systemd-stage-1

Fyi, a possible replacement for defaultPackages could be

https://github.com/NixOS/nixpkgs/pull/255086

It also allows users to remove packages, without breaking existing configs.

You'd be responsible for others' data loss because their backup script stopped working, as rsync disappeared.

Assuming they don't have any notification in place, and that nothing else installs rsync. But I agree, this is a concern. I still think it's really bad to install several effectively random and rarely used packages on every single NixOS instance.

We can't silently remove packages, and I don't think doing it loudly (whatever that is) is worth the annoyance for something as minor as this.

I wouldn't consider wasting however many cycles and bytes are needed for these packages millions or billions of times over "minor".

defaultPackages' purpose iirc is exactly to be able to opt out of these packages without breaking existing configurations.

The "opt out" is the problem here. I haven't seen any reason that any of these should be default, any more than Firefox, netcat, jq, or any of the thousands of available programs. And it's not exactly obvious to a beginner why this is necessary or how to do it.

Fyi, a possible replacement for defaultPackages could be
* [nixos/system-path: convert environment.systemPackages to an attrset #255086](https://github.com/NixOS/nixpkgs/pull/255086)

It also allows users to remove packages, without breaking existing configs.

That would be cool, but it's very far from ready, and we should still address the issue of installing packages which usually don't need to be there.

I agree that it's bad, but in my opinion the cure is worse.
At the very least, you should add a proper release note that describes what actually happens to people's configs.
(The changed line doesn't mean much to hardly anyone)
Maybe I'm wrong. Maybe others agree it's good enough? Feel free to discuss with others and reach a decision.

As I mentioned here, the original Idea behind defaultPackages was to gradually absorb things from requiredPackages one by one (checking that things do not break without them), allowing for them to be disabled be overriding defaultPackages and at the same time not breaking peoples setup (because they are still there by default).

Backwards compatibility is important but I don't want this to become another fgrep/egrep that is deprecated yet never removed.

And if the config just simply won't build because the option is gone

To be clear, that's not really the main scenario to care about when it comes to defaults, they're called default for a reason. The scenario to care about is those who didn't put rsync into their configs because it was already included in the base system (and who aren't using the rsyncd module, I suppose).

The scenario to care about is those who didn't put rsync into their configs because it was already included in the base system

If we really care a lot, then this change can be locked behind a state version, because changing it means you give consent to breaking changes.
And if we don't want to bloat NixOS code with state version checks that keep legacy code, then this change can be just another major release breaking change, people that upgrade from one major NixOS version to another also give their consent to breaking changes and should read release notes.
Although having perl of all things installed by default is not something that needs to be removed ASAP or else the user experience is ruined, I still don't want to see it be installed by default in 5 years despite it not being a dependency.


Changes in LastSeen / Online fields in the Headscale API

Hey!
Headscale dev here. Just a small heads up.
Since 0.23.0-alpha8, LastSeen is only updated when the node disconnects. This means the Online is now the indicator if the node is connected to headscale or not.
Of course, once a node is offline you can display the LastSeen data.

Resolved with #150 (thanks @ChxGuillaume )


Setup

I keep getting issues in the setting up. especially the base url and others. @jeffgodwyll  @JahlomP . See if you can get it up and running. The quick start guide is in a markdown "setup_install.md"
Hope we can begin little by little. and ge tthis done.

Noted John,
I shalt also take a look at it. Thanks for this man!
Regards,
Kobe
On Sun, Mar 22, 2015 at 6:59 PM, Jean Huit<EMAIL_ADDRESS>wrote:

I keep getting issues in the setting up. especially the base url and
others. @jeffgodwyll https://github.com/jeffgodwyll @JahlomP
https://github.com/JahlomP . See if you can get it up and running. The
quick start guide is in a markdown "setup_install.md"
Hope we can begin little by little. and ge tthis done.
--
Reply to this email directly or view it on GitHub
https://github.com/GDGGhana/Website/issues/2.

--
"An extraordinary life is one lived in services to others"
Owusu Subramaniam Kwabena ( KOBE)
g+: gplus.to/kobebigs
twitter: @kobebigs
skype: kobe_bigwig
www: http://kobebigs.com
*fone: *+233248317498 / +233265768096

Will look at it
On 16:18, Sun, Mar 22, 2015 Kobe Subramaniam<EMAIL_ADDRESS>wrote:

Noted John,
I shalt also take a look at it. Thanks for this man!
Regards,
Kobe
On Sun, Mar 22, 2015 at 6:59 PM, Jean Huit<EMAIL_ADDRESS>wrote:

I keep getting issues in the setting up. especially the base url and
others. @jeffgodwyll https://github.com/jeffgodwyll @JahlomP
https://github.com/JahlomP . See if you can get it up and running. The
quick start guide is in a markdown "setup_install.md"
Hope we can begin little by little. and ge tthis done.
--
Reply to this email directly or view it on GitHub
https://github.com/GDGGhana/Website/issues/2.

--
"An extraordinary life is one lived in services to others"
Owusu Subramaniam Kwabena ( KOBE)
g+: gplus.to/kobebigs
twitter: @kobebigs
skype: kobe_bigwig
www: http://kobebigs.com
*fone: *+233248317498 / +233265768096
—
Reply to this email directly or view it on GitHub
https://github.com/GDGGhana/Website/issues/2#issuecomment-84645034.

@JeanHuit OK. I'll look into it too. :+1:

Since no one got back here, i have changed things and am closing the issue.

ok
On Tue, Jun 2, 2015 at 3:01 PM Jean Huit<EMAIL_ADDRESS>wrote:

Closed #2 https://github.com/GDGGhana/Website/issues/2.
—
Reply to this email directly or view it on GitHub
https://github.com/GDGGhana/Website/issues/2#event-320049601.


add support for initialize hook

this PR adds support for the initialize hook: https://nodejs.org/api/esm.html#initialize
Essentially, with node v20.6 esmock does not need to be called with "--loader" and instead esmock creates its own message channel and script-registers the loader to the channel itself.

The newer initialize hook will really simplify many things and allow us to remove global variables and other things. For now though, things will get complicated.

This PR has a few major issues but is almost working. Observe current issues with esmock.node.global.test.js
./tests/tests-node/
npm run test-one esmock.node.global.test.js
npm run test-one-no--loader esmock.node.global.test.js

Main problem: currently, loader hooks engage three times and process files three times. This happens when "initialized" loader exports hooks used by "--loader" loader. If we did not need backward-compatibility, places needed by "--loader" could be removed and we would be done,

'esmock.js' should not export hook definitions unless "--loader" is used export * from './esmockLoader.js'
module.register should only be called one time by the top level caller, if no loader is already introduced by "--loader"
the error message should explain --loader is used with older versions of node

yikes node v20's globalPreload mechanism esmock uses to message the loader was removed this morning! https://github.com/nodejs/node/pull/49144

cautiously, this branch is mostly working... other things to consider adding here before this branch will be ready,

update the README, remove package.json example and include some message that links to the wiki for demonstrations of "--loader" that are required by older versions of node
update the error message that is thrown when loader is undefined, message something like "node versions earlier than v18.6 require the --loader hook; for more details see https://github.com/iambumblehead/esmock/wiki"
esmockLoader.js should be included and not-deleted from the published directory of files
the extra test runs that test "import.meta.resolve" should be removed and possibly these should be replaced with tests that call esmock without a --loader when node version is greater than 20.6

package.json scripts in the test folders are updated with patterns like this one used by the mocha folder
"scripts": {
  "isnodelt20_6": "node -e \"(([mj, mn]) => (+mj < 20 || (+mj === 20 && +mn < 6)))(process.versions.node.split('.')) || process.exit(1)\"",
  "test:loader": "mocha --loader=esmock",
  "test:current": "mocha",
  "test": "npm run test:loader && npm run isnodelt20_6 || npm run test:current"
}

This is kind of noisy however works well with windows and npm and for newer versions of node, runs tests without --loader=esmock. When support for node18 is dropped, a lot of noise can be removed from the sources and the script pattern can simplified to just this,
"scripts": {
  "test": "mocha"
}

please review :)

Planning to merge and publish this soon so changes will be available for the workspace PR https://github.com/iambumblehead/esmock/pull/243


Require Python version 3.6 or higher.

Don't commit to 4.0 yet.
Resolves #131

Sad that you don't want to support Py4 yet. Thanks!


effitask: init at 1.4.0

Motivation for this change
it looks like a good todo.txt gui :)

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I get a hash-mismatch when trying to build:
$ nix build --no-link --keep-going --option build-use-sandbox relaxed -f /home/phoenix/.cache/nixpkgs-review/pr-84291/build.nix
hash mismatch in fixed-output derivation '/nix/store/vnb83xkhpmafcigva15javzw0f90j6nb-effitask-1.4.0-vendor.tar.gz':
  wanted: sha256:1crp43577k6ggywmdrphnfa8q353shj7746q07bv2vgbj84qqnqn
  got:    sha256:0dvmp23kny6rlv6c0mfyy3cmz1bi5wcm1mxps4z67lym5kxfd362
cannot build derivation '/nix/store/6qlm90gfg48b1nlkd9d0c0f2xpv1rxa3-effitask-1.4.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/fyr7p1l5ch6mvyi9znnl266xga367il4-env.drv': 1 dependencies couldn't be built
[1 built (1 failed), 132 copied (1454.1 MiB), 395.2 MiB DL]
error: build of '/nix/store/fyr7p1l5ch6mvyi9znnl266xga367il4-env.drv' failed
https://github.com/NixOS/nixpkgs/pull/84291
1 package failed to build:
effitask

@Emantor thanks for your effort to test this!
That is strange. The hash is correct when i build it using nix-env -f ~/code/nixpkgs -i effitask.
installing
hash mismatch in fixed-output derivation '/nix/store/5yvbxh2q627ppk5jvwfk7gpdjphpkv1y-effitask-1.4.0-vendor.tar.gz':
  wanted: sha256:0000000000000000000000000000000000000000000000000000
  got:    sha256:1crp43577k6ggywmdrphnfa8q353shj7746q07bv2vgbj84qqnqn
cannot build derivation '/nix/store/wyxm09hv0vcm0q5vw5yb7a3g7h7x7yrd-effitask-1.4.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/wyxm09hv0vcm0q5vw5yb7a3g7h7x7yrd-effitask-1.4.0.drv' failed

And don't get the error with nix-shell -p nixpkgs-review --run "nixpkgs-review pr 84291".
...
Automatic merge went well; stopped before committing as requested
$ nix build --no-link --keep-going --option build-use-sandbox relaxed -f /home/davidak/.cache/nixpkgs-review/pr-84291/build.nix
warning: ignoring the user-specified setting 'sandbox', because it is a restricted setting and you are not a trusted user
[2 built, 224 copied (1890.5 MiB), 485.3 MiB DL]
https://github.com/NixOS/nixpkgs/pull/84291
1 package built:
effitask

What could be the difference here?

@davidak are you on stable or unstable? I'm running NixOS unstable.

@Emantor i'm on stable.
nixpkgs-review has the same version.
$ nix run -f channel:nixos-19.09 nixpkgs-review
$ which nixpkgs-review
/nix/store/35vbwh8hmy935xhh6xd5x65c74iz597g-nixpkgs-review-2.2.0/bin/nixpkgs-review

$ nix run -f channel:nixos-unstable nixpkgs-review
$ which nixpkgs-review
/nix/store/9ywlmbslln9va0i2kmbj9gz1bdc40a44-nixpkgs-review-2.2.0/bin/nixpkgs-review

Maybe the Nix version?
$ nix --version
nix (Nix) 2.3.3

I suspect there were some changes pertaining to cargo-vendor. Stable still contains cargo-vendor while master has dropped it for the builtin support in cargo version 1.37.

@Emantor but the PR is branched from master, so it shouldn't make a difference? Or does nixpkgs-review build the changes of the PR on the current system channel?

Indeed, cargo should be used from master too. Maybe @alyssais has an idea?  (pinging because she did some cargo sha fixups on master, found by a quick git log --grep)

I had access to a machine with nixos unstable and was able to reproduce the error. Updated it to work on master.
To run it properly, it has to be installed. in nix shell are assets not found. it also neede configured todo.txt-cli (see readme)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/250


Prompt caching with Batch API ?

Hey there,
I see I get a system.0.cache_control: Extra inputs are not permitted or messages.0.cache_control: Extra inputs are not permitted when trying to use the cache_control with the Batch API. Is this by design? Looking at the docs I should be able to: https://docs.anthropic.com/en/docs/build-with-claude/message-batches#can-i-use-the-message-batches-api-in-conjunction-with-other-betas
My code:
await anthropic.beta.messages.batches.create({
  requests: [
    {
      custom_id: some_id,
      params: {
        betas: ['prompt-caching-2024-07-31', 'message-batches-2024-09-24'],
        model: 'claude-3-5-sonnet-20240620',
        max_tokens: 100,
        system: [
          {
            text: very_long_text,
            type: 'text',
            cache_control: {
              type: 'ephemeral'
            }
          }
        ],
        messages: [
          {
            role: 'user',
            content: 'What is this very long text?',
          }
        ]
      }
    },
  ]
})

@clonecorp you should move the "betas" field out of the request:
await anthropic.beta.messages.batches.create({
  betas: ['prompt-caching-2024-07-31', 'message-batches-2024-09-24'],
  requests: [
    {
      custom_id: some_id,
      params: {
        model: 'claude-3-5-sonnet-20240620',
        max_tokens: 100,
        system: [
          {
            text: very_long_text,
            type: 'text',
            cache_control: {
              type: 'ephemeral'
            }
          }
        ],
        messages: [
          {
            role: 'user',
            content: 'What is this very long text?',
          }
        ]
      }
    },
  ]
})

@clonecorp you should move the "betas" field out of the request

Ahhh, I see. It works now. Thanks!


GitHub Terms of Service - GitHub Docs

Skip to main content
GitHub Docs
Site policy/GitHub Terms/GitHub Terms of Service
GitHub Terms of Service
In this article
Summary
The GitHub Terms of Service
A. Definitions
B. Account Terms
C. Acceptable Use
D. User-Generated Content
E. Private Repositories
F. Copyright Infringement and DMCA Policy
G. Intellectual Property Notice
H. API Terms
I. GitHub Additional Product Terms
J. Beta Previews
K. Payment
L. Cancellation and Termination
M. Communications with GitHub
N. Disclaimer of Warranties
O. Limitation of Liability
P. Release and Indemnification
Q. Changes to These Terms
R. Miscellaneous
Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users, we have tried to make it as clear as possible. For your convenience, we have presented these terms in a short non-binding summary followed by the full legal terms.
Summary
Section	What can you find there?
A. Definitions	Some basic terms, defined in a way that will help you understand this agreement. Refer back up to this section for clarification.
B. Account Terms	These are the basic requirements of having an Account on GitHub.
C. Acceptable Use	These are the basic rules you must follow when using your GitHub Account.
D. User-Generated Content	You own the content you post on GitHub. However, you have some responsibilities regarding it, and we ask you to grant us some rights so we can provide services to you.
E. Private Repositories	This section talks about how GitHub will treat content you post in private repositories.
F. Copyright & DMCA Policy	This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub.
G. Intellectual Property Notice	This describes GitHub's rights in the website and service.
H. API Terms	These are the rules for using GitHub's APIs, whether you are using the API for development or data collection.
I. Additional Product Terms	We have a few specific rules for GitHub's features and products.
J. Beta Previews	These are some of the additional terms that apply to GitHub's features that are still in development.
K. Payment	You are responsible for payment. We are responsible for billing you accurately.
L. Cancellation and Termination	You may cancel this agreement and close your Account at any time.
M. Communications with GitHub	We only use email and other electronic means to stay in touch with our users. We do not provide phone support.
N. Disclaimer of Warranties	We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.
O. Limitation of Liability	We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.
P. Release and Indemnification	You are fully responsible for your use of the service.
Q. Changes to these Terms of Service	We may modify this agreement, but we will give you 30 days' notice of material changes.
R. Miscellaneous	Please see this section for legal details including our choice of law.
The GitHub Terms of Service
Effective date: November 16, 2020
A. Definitions
Short version: We use these basic terms throughout the agreement, and they have specific meanings. You should know what we mean when we use each of the terms. There's not going to be a test on it, but it's still useful information.
An "Account" represents your legal relationship with GitHub. A “Personal Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A Personal Account can be a member of any number of Organizations.
The “Agreement” refers, collectively, to all the terms, conditions, notices contained or referenced in this document (the “Terms of Service” or the "Terms") and all other operating rules, policies (including the GitHub Privacy Statement, available at github.com/site/privacy) and procedures that we may publish from time to time on the Website. Most of our site policies are available at docs.github.com/categories/site-policy.
"Beta Previews" mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings.
“Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. "Content" also includes Services. “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. "Your Content" is Content that you create or own.
“GitHub,” “We,” and “Us” refer to GitHub, Inc., as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees.
The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews.
“The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. A User must be at least 13 years of age. Special terms may apply for business or government Accounts (See Section B(5): Additional Terms).
The “Website” refers to GitHub’s website located at github.com, and all content, services, and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com, such as education.github.com and pages.github.com. These Terms also govern GitHub’s conference websites, such as githubuniverse.com, and product websites, such as electronjs.org. Occasionally, websites owned by GitHub may provide different or additional terms of service. If those additional terms conflict with this Agreement, the more specific terms apply to the relevant page or service.
B. Account Terms
Short version: Personal Accounts and Organizations have different administrative controls; a human must create your Account; you must be 13 or over; you must provide a valid email address; and you may not have more than one free Account. You alone are responsible for your Account and anything that happens while you are signed in to or using your Account. You are responsible for keeping your Account secure.

Account Controls
Users. Subject to these Terms, you retain ultimate administrative control over your Personal Account and the Content within it.

Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one Personal Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization.

Required Information
You must provide a valid email address in order to complete the signup process. Any other information requested, such as your real name, is optional, unless you are accepting these terms on behalf of a legal entity (in which case we need more information about the legal entity) or if you opt for a paid Account, in which case additional information will be necessary for billing purposes.

Account Requirements
We have a few simple rules for Personal Accounts on GitHub's Service.

 Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts:
A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free Personal Account.
One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine).
You must be age 13 or older. While we are thrilled to see brilliant young coders get excited by learning to program, we must comply with United States law. GitHub does not target our Service to children under 13, and we do not permit any Users under 13 on our Service. If we learn of any User under the age of 13, we will terminate that User’s Account immediately. If you are a resident of a country outside the United States, your country’s minimum age may be older; in such a case, you are responsible for complying with your country’s laws.
Your login may only be used by one person — i.e., a single login may not be shared by multiple people. A paid Organization may only provide access to as many Personal Accounts as your subscription allows.
You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a Specially Designated National (SDN) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency. GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations. For more information, please see our Export Controls policy.
4. Account Security
You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you.
You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account).
You are responsible for maintaining the security of your Account and password. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation.
You will promptly notify GitHub by contacting us through the GitHub Support portal if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account.
5. Additional Terms
In some situations, third parties' terms may apply to your use of GitHub. For example, you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub to authenticate to another service.
If you are a government User or otherwise accessing or using any GitHub Service in a government capacity, this Government Amendment to GitHub Terms of Service applies to you, and you agree to its provisions.
If you have signed up for GitHub Enterprise Cloud, the Enterprise Cloud Addendum applies to you, and you agree to its provisions.
C. Acceptable Use
Short version: GitHub hosts a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the service, you must follow the terms of this section, which include some restrictions on content you can post, conduct on the service, and other limitations. In short, be excellent to each other.
Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your use of the Service is in compliance with laws and any applicable regulations.
You agree that you will not under any circumstances violate our Acceptable Use Policies or Community Guidelines.
D. User-Generated Content
Short version: You own content you create, but you allow us certain rights to it, so that we can display and share the content you post. You still have control over your content, and responsibility for it, and the rights you grant us are limited to those we need to provide the service. We have the right to remove content or close Accounts if we need to.

Responsibility for User-Generated Content
You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content.

GitHub May Remove Content
We have the right to refuse or remove any User-Generated Content that, in our sole discretion, violates any laws or GitHub terms or policies. User-Generated Content displayed on GitHub Mobile may be subject to mobile app stores' additional terms.

Ownership of Content, Right to Post, and License Grants
You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post.

Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other GitHub Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it.

License Grant to Us
We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video.

This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program.

License Grant to Other Users
Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).

If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you adopt a license. If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.

Contributions Under Repository License
Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. If you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede.

Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit.

Moral Rights
You retain all moral rights to Your Content that you upload, publish, or submit to any part of the Service, including the rights of integrity and attribution. However, you waive these rights and agree not to assert them against us, to enable us to reasonably exercise the rights granted in Section D.4, but not otherwise.

To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights we need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service.
E. Private Repositories
Short version: We treat the content of private repositories as confidential, and we only access it as described in our Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with our legal obligations, if we have reason to believe the contents are in violation of the law, or with your consent.

Control of Private Repositories
Some Accounts may have private repositories, which allow the User to control access to Content.

Confidentiality of Private Repositories
GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care.

Access
GitHub personnel may only access the content of your private repositories in the situations described in our Privacy Statement.

You may choose to enable additional access to your private repositories. For example:
You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the GitHub Service, we will provide an explanation of those rights.
Additionally, we may be compelled by law to disclose the contents of your private repositories.
GitHub will provide notice regarding our access to private repository content, unless for legal disclosure, to comply with our legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
F. Copyright Infringement and DMCA Policy
If you believe that content on our website violates your copyright, please contact us in accordance with our Digital Millennium Copyright Act Policy. If you are a copyright owner and you believe that content on GitHub violates your rights, please contact us via our convenient DMCA form or by emailing<EMAIL_ADDRESS>There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses.
We will terminate the Accounts of repeat infringers of this policy.
G. Intellectual Property Notice
Short version: We own the service and all of our content. In order for you to use our content, we give you certain rights to it, but you may only use our content in the way we have allowed.

GitHub's Rights to Content
GitHub and our licensors, vendors, agents, and/or our content providers retain ownership of all intellectual property rights of any kind related to the Website and Service. We reserve all rights that are not expressly granted to you under this Agreement or by law. The look and feel of the Website and Service is copyright © GitHub, Inc. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, Javascript, or visual design elements or concepts without express written permission from GitHub.

GitHub Trademarks and Logos
If you’d like to use GitHub’s trademarks, you must follow all of our trademark guidelines, including those on our logos page: https://github.com/logos.

License to GitHub Policies
This Agreement is licensed under this Creative Commons Zero license. For details, see our site-policy repository.

H. API Terms
Short version: You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Provider Interface), including use of the API through a third party product that accesses GitHub.
Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub, in our sole discretion, will determine abuse or excessive usage of the API. We will make a reasonable attempt to warn you via email prior to suspension.
You may not share API tokens to exceed GitHub's rate limitations.
You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards.
All use of the GitHub API is subject to these Terms of Service and the GitHub Privacy Statement.
GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service.
I. GitHub Additional Product Terms
Short version: You need to follow certain specific terms and conditions for GitHub's various features and products, and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.
Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services, you also agree to the GitHub Additional Product Terms.
J. Beta Previews
Short version: Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.

Subject to Change
Beta Previews may not be supported and may be changed at any time without notice. In addition, Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. By using a Beta Preview, you use it at your own risk.

Confidentiality
As a user of Beta Previews, you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information, it’s important for us to make sure that you keep that information secret.

Confidentiality Obligations. You agree that any non-public Beta Preview information we give you, such as information about a private Beta Preview, will be considered GitHub’s confidential information (collectively, “Confidential Information”), regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”), and not for any other purpose. You should use the same degree of care as you would with your own confidential information, but no less than reasonable precautions to prevent any unauthorized use, disclosure, publication, or dissemination of our Confidential Information. You promise not to disclose, publish, or disseminate any Confidential Information to any third party, unless we don’t otherwise prohibit or restrict such disclosure (for example, you might be part of a GitHub-organized group discussion about a private Beta Preview feature).
Exceptions. Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law, provided GitHub has been given reasonable advance written notice to object, unless prohibited by law.

Feedback
We’re always trying to improve of products and services, and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for our products or services (collectively, “Feedback”), you acknowledge and agree that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit and/or incorporate the Feedback into our products, services, and documentation.

K. Payment
Short version: You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately, and letting you know well in advance if those prices change.

Pricing
Our pricing and payment terms are available at github.com/pricing. If you agree to a subscription price, that will remain your price for the duration of the payment term; however, prices are subject to change at the end of a payment term.

Upgrades, Downgrades, and Changes
We will immediately bill you when you upgrade from the free plan to any paying plan.
If you change from a monthly billing plan to a yearly billing plan, GitHub will bill you for a full year at the next monthly billing date.
If you upgrade to a higher level of service, we will bill you for the upgraded plan immediately.
You may change your level of service at any time by choosing a plan option or going into your Billing settings. If you choose to downgrade your Account, you may lose access to Content, features, or capacity of your Account. Please see our section on Cancellation for information on getting a copy of that Content.

Billing Schedule; No Refunds
Payment Based on Plan For monthly or yearly payment plans, the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service, downgrade refunds, or refunds for months unused with an open Account; however, the service will remain active for the length of the paid billing period. In order to treat everyone equally, no exceptions will be made.

Payment Based on Usage Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to use paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See GitHub Additional Product Terms for Details.
Invoicing For invoiced Users, User agrees to pay the fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If User fails to pay any fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable order form. User is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement.

Authorization
By agreeing to these Terms, you are giving us permission to charge your on-file credit card, PayPal account, or other approved methods of payment for fees that you authorize for GitHub.

Responsibility for Payment
You are responsible for all fees, including taxes, associated with your use of the Service. By using the Service, you agree to pay GitHub any charge incurred in connection with your use of the Service. If you dispute the matter, contact us through the GitHub Support portal. You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information.

L. Cancellation and Termination
Short version: You may close your Account at any time. If you do, we'll treat your information responsibly.

Account Cancellation
It is your responsibility to properly cancel your Account with GitHub. You can cancel your Account at any time by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request.

Upon Cancellation
We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information can not be recovered once your Account is canceled.

We will not delete Content that you have contributed to other Users' repositories or that other Users have forked.
Upon request, we will make a reasonable effort to provide an Account owner with a copy of your lawful, non-infringing Account contents after Account cancellation, termination, or downgrade. You must make this request within 90 days of cancellation, termination, or downgrade.

GitHub May Terminate
GitHub has the right to suspend or terminate your access to all or any part of the Website at any time, with or without cause, with or without notice, effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time.

Survival
All provisions of this Agreement which, by their nature, should survive termination will survive termination — including, without limitation: ownership provisions, warranty disclaimers, indemnity, and limitations of liability.

M. Communications with GitHub
Short version: We use email and other electronic means to stay in touch with our users.

Electronic Communication Required
For contractual purposes, you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service, agreements, notices, disclosures, and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights.

Legal Notice to GitHub Must Be in Writing
Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers, employees, agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and served on GitHub's legal agent.

No Phone Support
GitHub only offers support via email, in-Service communications, and electronic messages. We do not offer telephone support.

N. Disclaimer of Warranties
Short version: We provide our service as is, and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.
GitHub provides the Website and the Service “as is” and “as available,” without warranty of any kind. Without limiting this, we expressly disclaim all warranties, whether express, implied or statutory, regarding the Website and the Service including without limitation any warranty of merchantability, fitness for a particular purpose, title, security, accuracy and non-infringement.
GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted, timely, secure, or error-free; that the information provided through the Service is accurate, reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files, information, content or other material obtained from the Service.
O. Limitation of Liability
Short version: We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.
You understand and agree that we will not be liable to you or any third party for any loss of profits, use, goodwill, or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from
the use, disclosure, or display of your User-Generated Content;
your use or inability to use the Service;
any modification, price change, suspension or discontinuance of the Service;
the Service generally or the software or systems that make the Service available;
unauthorized access to or alterations of your transmissions or data;
statements or conduct of any third party on the Service;
any other user interactions that you input or receive through your use of the Service; or
any other matter relating to the Service.
Our liability is limited whether or not we have been informed of the possibility of such damages, and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control.
P. Release and Indemnification
Short version: You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else, we will not be involved.
If you have a dispute with one or more Users, you agree to release GitHub from any and all claims, demands and damages (actual and consequential) of every kind and nature, known and unknown, arising out of or in any way connected with such disputes.
You agree to indemnify us, defend us, and hold us harmless from and against any and all claims, liabilities, and expenses, including attorneys’ fees, arising out of your use of the Website and the Service, including but not limited to your violation of this Agreement, provided that GitHub (1) promptly gives you written notice of the claim, demand, suit or proceeding; (2) gives you sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that you may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance, at your expense.
Q. Changes to These Terms
Short version: We want our users to be informed of important changes to our terms, but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time, we will notify users of any material changes and give you time to adjust to them.
We reserve the right, at our sole discretion, to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement, such as price increases, at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications, your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our Site Policy repository.
We reserve the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Website (or any part of it) with or without notice.
R. Miscellaneous

Governing Law
Except to the extent applicable law provides otherwise, this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California, without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco, California.

Non-Assignability
GitHub may assign or delegate these Terms of Service and/or the GitHub Privacy Statement, in whole or in part, to any person or entity at any time with or without your consent, including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent, and any unauthorized assignment and delegation by you is void.

Section Headings and Summaries
Throughout this Agreement, each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding.

Severability, No Waiver, and Survival
If any part of this Agreement is held invalid or unenforceable, that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement.

Amendments; Complete Agreement
This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub, or by the posting by GitHub of a revised version in accordance with Section Q. Changes to These Terms. These Terms of Service, together with the GitHub Privacy Statement, represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written, and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements.

Questions
Questions about the Terms of Service? Contact us through the GitHub Support portal.

Press alt+up to activate
Help and support
Help us make these docs great!
All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.
Learn how to contribute
Still need help?
Ask the GitHub community
Contact support
Legal
© 2023 GitHub, Inc.
Terms
Privacy
Status
Pricing
Expert services
Blog

<EMAIL_ADDRESS>Follow all terms of service holdings with all fixed made by<EMAIL_ADDRESS>> ````


Is it possible to invite people to sign the CLA who have opened or commented on an issue?

Contribution to open source projects come in many forms, not all of which are covered by a Pull Request.
So, I would like to ask all commenters on issues to also sign the CLA.
Has anyone actually tried this?

This could be a good addition.  There isn't the same PR workflow that has checks, but the CLA assistant could do one or both of:

update a comment
update a label: cla-unsigned or something


[Go live][26 May]

Push to live

Docs Build status updates of commit 4acaefa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/Media/mobile-bot-menu-sample.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/create-a-bot-commands-menu.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


boost::filesystem missing dependency to boost::system

boost::filesystem-vcXXX has a dependency to boost::system-vcXXX
it dose not compile without it
but in nuget package dependency isn't visible, boost::system had be installed manually

It's not a bug, it's a feature :-) In some cases, you don't want to use boost_system-vsXXX NuGet package. For example, if you compile it yourself or use boost_system-src package.

I don't want to be a nag, but I would expect that one would either use all from nuget or build boost from source. Even if this wouldn't be true, I think most uses that just wan't to use boost:filesytem want just get it with dependencies as simple as possible and nuget package fulfills it. Following Your login, then any nuget package shouldn't have any dependencies because maybe you want to compile it from source. But so as You think.


Add multiple Objects/ Coordinates / pinCoordinate ?

Hey,
i cant handle to insert multiple objects as in the demo GIF like Canary Wharf, O2 Arena, City of London etc.
How did you do that?
Best regards,
Thomas

Hey, so I had multiple objects I added by using a for each loop. Check out my code, though yours may differ:
`cords.forEach { (cord) in
        let location = CLLocation(coordinate: cord, altitude: 60)

        let distance = location.distance(from: loc!)

        //804 is in meters - equal to half a mile
        if distance <= 804 {
            let annotationNode = LocationAnnotationNode(location: location, image: image)
            sceneLocationView.addLocationNodeWithConfirmedLocation(locationNode: annotationNode)
        }

    }`


chore(main): release cyclistsofmsn-backend 1.0.8

:robot: I have created a release beep boop
1.0.8 (2024-04-02)
Bug Fixes

bump date-fns from 3.5.0 to 3.6.0 (d1ecf6a)
bump date-fns from 3.5.0 to 3.6.0 (745a86b)
bump pino-pretty from 10.3.1 to 11.0.0 (d47a07f)
bump pino-pretty from 10.3.1 to 11.0.0 (d2f31db)
more strict lint fixes (b49a1dc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/madisonbikes/cyclistsofmsn-backend/releases/tag/cyclistsofmsn-backend-v1.0.8 :sunflower:


[6.x] Dispatch MessageProcessing event before the message is sent

This PR dispatches a new Illuminate\Mail\Events\MessageProcessing event to add an opportunity to change the message just before it is sent.
A use case for this is when there are global changes that need to be applied to all messages.
In my case, I needed to add a BCC address to all outgoing emails, and I couldn't find a way to do it except extending the mailer class. But with this new event, it will be much easier:
class EventServiceProvider extends ServiceProvider
{
    ...
    public function boot()
    {
        parent::boot();

        Event::listen(MessageProcessing::class, function($event) {
            $event->message->addBcc('test@example.com');
        });
    }
}

Note: There's a MessageSending event but it's for shouldSendMessage method, and it's dispatched using $this->events->until, so it means that some listeners may be skipped.

I like the PR.
But even without the event you can add a global bcc. You create a base mail class instead of the Mailable and in the build method you add the bcc and all your emails will extend this base class.
But +1 for you, using events is cleaner and better.

Extending core classes like that is usually not such a great idea. The event hook is probably the best approach.

I really would rather just make MessageSending work for this use case instead of introducing another event.


Create sidebars-zh_cn.js

Which pr
?

are you sure your sidebar will work? 🤔

no, idk too🤔
uhhhhhhhhhhhh

試一試吧

I'm not sure about that, but u can checkout the how the docs recommended to do i18n;
https://www.docusaurus.cn/docs/i18n/introduction

試一試吧

Sure


Addon menus are white

Hi
I have installed the theme from AUR it was working fine until I had to reset firefox settings to default from about:support menu. After that I used the updater to uninstall shadow fox theme then reapply. Some main menus are now black like they are suppose to be but for example ublock settings is white and menu you enter to block stuff etc. Noscript menu is default white.
Any ideas to fix?

Make sure you are using the Firefox dark theme
Make sure you are using the correct profile for installing (you can go to about:profiles to see your active profile)

seems to be correct..

Is the "Auto-Generate UUIDs" option checked?

Thanks, that fixed it! Greasemonkey looks better now, too.

Is the "Auto-Generate UUIDs" option checked?

Is there a reason this is not checked by default?

The "Auto-generate UUID's" option removes any customizations you have in internal_UUIDs.txt, so it's safer to have it opt-in. Some people choose to manually edit the file so that only certain extensions get styled.

Hmm. Can you go to the root folder (click "open directory"on about:profiles) and tell me what's in the chrome folder?

Sorry for late reply but I fixed my issue by deleting folder /home/steve/.mozilla/firefox/hpcy9bdp.default-1531243544800/chrome/ after that I reapplied the shadowfox updater and it worked just fine! must have been some issue from reseting the profile to default then it might have left some ghost things behind?

Looks like the issues have been resolved, feel free to re-open if I'm missing something.
Thanks for the help @SrKomodo!


EntityComponent doesn't respect entity_namespace for dynamically loaded entities

Home Assistant release (hass --version):
0.59.2
Python release (python3 --version):
3.6.3
Component/platform:
helpers/entity_component
Description of problem:
Devices discovered dynamically after initial setup do not respect the entity_namespace config.
Expected:
Devices discovered always have the correct entity namespace if configured.
Problem-relevant configuration.yaml entries and steps to reproduce:
media_player:
- platform: cast
  entity_namespace: 'cast'

Unplug one of the chromecast
Start Home assistant and wait until cast devices are discovered and setup
Plug the chromecast and wait for it to be discovered

Relevant Log:
2017-12-06 11:28:01 INFO (MainThread) [homeassistant.core] Bus:Handling <Event platform_discovered[L]: service=load_platform.media_player, platform=cast, discovered=host=xxx.xxx.xxx.xxx, port=8009, hostname=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.local., properties=id=xxxxxxxxxxxxxxxxxxx, cd=XXXXXXXXXXXXXXXXXXXXX, rm=False, ve=05, md=ADT-1, ic=/setup/icon.png, fn=Mathieu ADT-1, ca=8197, st=0, bs=XXXXXXXXXXXX, nf=1, rs=False>
2017-12-06 11:28:01 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.cast
2017-12-06 11:28:12 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.mathieu_adt1, old_state=None, new_state=<state media_player.mathieu_adt1=off; friendly_name=Mathieu ADT-1, supported_features=21437 @ 2017-12-06T11:28:12.908789-08:00>>

Additional info:
I personally have this problem for my cast devices, but looking into why this happens, all entities that rely on the default naming should be affected.
The problem seem to be that in EntityComponent.async_setup, the component_platform_discovered callback doesn't include the platform_config when it invokes the private _async_setup_platform helper. In that helper, the entity_namespace is used to key the lookup of existing platform instances.

In theory #12313 should fix this for the new entity registry.
In the case of cast, #12474 should fix all related issues.
I haven't updated to 0.64 yet and will report as soon as I do.


Use screen instead of destructing render

Use screen instead of destructing render
:recycle: Current situation & Problem
Destructing render to get selectors  binds result of render to selectors. Sometimes it's unwanted, especially if creating some reusable functions across the tests.
This binding is completely unnecessary, doesn't benefit tests readability and ease of development. It's easier to use screen everywhere, because of auto-completion and lack of maintenance of destructed properties.
:gear: Release Notes

Use screen instead of destructing render

Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

This is a nice improvement - thanks @arkadiuszbachorski!


Upgrade to geojs 0.12.3 and improve line annotations.

This handles line annotations that are closed.

Codecov Report

Merging #207 into master will increase coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #207      +/-   ##
==========================================
+ Coverage   89.07%   89.08%   +<.01%
==========================================
  Files          53       53
  Lines        3360     3362       +2
  Branches       88       89       +1
==========================================
+ Hits         2993     2995       +2
  Misses        367      367

Impacted Files
Coverage Δ

web_client/annotations/geojs/types/line.js
100% <ø> (ø)
:arrow_up:

web_client/views/imageViewerWidget/geojs.js
97.45% <50%> (-0.82%)
:arrow_down:

server/tilesource/tiff_reader.py
86.85% <0%> (-0.4%)
:arrow_down:

web_client/views/imageViewerWidget/slideatlas.js
84.61% <0%> (+7.69%)
: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 970581a...905d4fa. Read the comment docs.


Hooks Refactor - PR

Math Magicians: refactor with hooks
Completed refactoring Calculator.js file from class-based to Hooks

Refactor the Calculator component (components/Calculator.js) from a class-based component to a functional component with hooks.
After the refactor I've tested the app in the browser. It works well.

Thanks


chore(contracts): Inconsistent ordering of functions in AbstractPortal

What does this PR do?
Optimizes the ordering of hooks in the Abstract Portals to make them more readable
Related ticket
Fixes #829
Type of change

[X] Chore
[ ] Bug fix
[ ] New feature
[ ] Documentation update

Check list

[ ] Unit tests for any smart contract change
[ ] Contracts and functions are documented

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.55%. Comparing base (7f57adb) to head (13fb1ee).

Additional details and impacted files
@@             Coverage Diff             @@
##              dev     #831       +/-   ##
===========================================
+ Coverage   48.96%   74.55%   +25.58%
===========================================
  Files          18       49       +31
  Lines         388      892      +504
  Branches       61      187      +126
===========================================
+ Hits          190      665      +475
- Misses        195      224       +29
  Partials        3        3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Show Matroska track enabled flag

This flag is current not shown. Could you please show it when present in the header and value is false? This would greatly help diagnose playback problems for files where tracks have mistakenly been set as disabled. I have encountered several users with such issues already.

But this flag could be later changed on the fly by the "Control Track", so it is temporary.
But maybe if I also check that there is no "Control Track", it would mean a manipulation error.
Sample file? I need only few first KB of the file.

Sample


HHH-18444 Remove deprecate Session#refresh methods

Remove deprecate Session#refresh methods

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

https://hibernate.atlassian.net/browse/HHH-18444

Fixed conflict locally and pushed.
Thanks :)


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In c133a97, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 6301 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in efbc168.


Build error with clang++ 17

Hello,
those lines in schema/config-schema.json are problematic in C++:
                    "required": [
                        "class"
                    ],
                    "properties": {
                        "class": {

"class" is a reserved c++ keyword, and thus the generated header-file triggers an error when trying to compile with clang++ 17:
/usr/include/ocispec/runtime_spec_schema_config_schema.h:140:11: error: expected member name or ';' after declaration specifiers
|   140 |     char *class;
|       |     ~~~~  ^
| 1 error generated.

As far as I understand, since the generated header-file contains "#ifdef __cplusplus", it is supposed to be parseable by a c++ compiler.

@Ecordonnier Is there anything we can do?

Just renaming class to ioprioclass is enough.  I'll send a patch once I've gone through the upstreaming review process at my company.

Unfortunately I'm not aware of another way to make this file compile with clang++ (other than patching clang). Currently it is not a valid c++ file.

How about writing the parser by hand instead of auto-generating it?.

In fact, both Rust and Go do.

Needs more reason.


Explain the importance of requireProofKey

The importance of making PKCE required is explained at https://www.ietf.org/archive/id/draft-ietf-oauth-security-topics-22.html#name-pkce-downgrade-attack

Thanks for the update @weltonrodrigo. This is now merged.


Migration task

There's need to implement migration task.
Task should be run on install, and perform check if there already is customfield 'Risk', and if it's appropriate type. If it's not, it should get every issue that uses invalid task and convert it to valid.

If there are risks with different custom field type, IndexOutOfBoundsException occurs, as fallows:
2015-06-27 09:03:35,766 ajp-bio-18009-exec-127 ERROR admin 543x35096x1 1ikn21d <IP_ADDRESS> /rest/jira-risk-management/1.0/controller/matrix [plugins.jrmp.rest.JRMPRisk
ManagementController] getMatrix: The Matrix couldn't be generated because of: Index: 5, Size: 5
java.lang.IndexOutOfBoundsException: Index: 5, Size: 5
at java.util.LinkedList.entry(LinkedList.java:365)
at java.util.LinkedList.get(LinkedList.java:315)
at net.amg.jira.plugins.jrmp.services.model.RiskIssuesModel.fillAllFields(RiskIssuesModel.java:115)
at net.amg.jira.plugins.jrmp.services.model.RiskIssuesModel.(RiskIssuesModel.java:53)
at net.amg.jira.plugins.jrmp.services.MatrixGeneratorImpl.generateMatrix(MatrixGeneratorImpl.java:107)
Migration task should find all of those issues and migrate them to used custom field type.


FIX: New rule on the number of members in the Steering Committee + Typo fixes

Fix typos in CHARTER.md, PROJECT-CHARTER.md, README.md
Fix the last row of the table in MAINTAINERS.md
Add new rule on the number of members in the Steering committee (>=3 and odd)

Thanks a lot for the review! I don't have write access to this repository. Would it be possible to merge it for me?


Is there a solution to edit vue code online?

https://twitter.com/haoqunjiang/status/1415684440529924117


Create Rain Water Trapping Problem arrays.md

This is the code for famous rainwater traping problem. pls add it to the above repository

pls give the hactoberfest accepted label

please give me this issue


yield model from

Example use case:
<BsForm @model={{hash}} as |form|>
  <form.element @controlType="date" @property="start" />
  <form.element @controlType="date" @property="end" as |el|>
   <el.control min={{form.model.start}} />
  </form.element>
</BsForm>

I'm not sure how to document this best. :confused: @simonihmig, do you have any suggestions?

I am not against adding this, but FWIW I think you could easily workaround this using the let helper:
{{#let (hash) as |model|}}
<BsForm @model={{model}} as |form|>
  <form.element @controlType="date" @property="start" />
  <form.element @controlType="date" @property="end" as |el|>
   <el.control min={{model.start}} />
  </form.element>
</BsForm>
{{/let}}

I'm not sure how to document this best. 😕 @simonihmig, do you have any suggestions?

Nothing better than mentioning it in the API docs somewhere here: https://github.com/kaliber5/ember-bootstrap/blob/master/addon/components/base/bs-form.js
We could explicitly list all the yielded values, including the yielded components (group and element). Eventually we will start to yield more, like button...

I am not against adding this, but FWIW I think you could easily workaround this using the let helper:

You are right. I totally missed that obvious solution. I think we should not unnecessary bloat the API surface.


Virtualmin Git plugin error

When the Virtualmin Git plugin is installed, clicking on "Repository Commands" or "Browse Repository" it will display an error page with the message: "No button clicked!"
This error is only displayed when using the authentic theme. I used version 4.2.0.

Virtualmin version 5.02 .... same

What theme version you're having installed?

Authentic Theme 18.00
Webmin 1.795
Virtualmin 5.02
In Centos 6.7
De: Ilia Rostovtsev<EMAIL_ADDRESS>Enviado el: jueves, 08 de septiembre de 2016 20:19
Para: qooob/authentic-theme<EMAIL_ADDRESS>CC: recursosformacion<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Asunto: Re: [qooob/authentic-theme] Virtualmin Git plugin error (#16)
What theme version you're having installed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/qooob/authentic-theme/issues/16#issuecomment-245690239 , or mute the thread https://github.com/notifications/unsubscribe-auth/ATqop2ykIouSwTrqc5V-rgJS0zZTTlBEks5qoFGWgaJpZM4CyVKE .

No wonder you have those issue.
Upgrade to the latest Webmin 1.810 (shipped with latest Authentic Theme 18.10).

I'm seeing the same problem.
CentOS 6.8
Webmin 1.810
Virtualmin 5.04
Authentic 18.10

Dupe #https://github.com/qooob/authentic-theme/issues/546

It will be fixed in 18.20

Error
No button clicked!
I have also same issue and kindly tel us at least how to fix it.
Thank you in advanced

Just upgrade to theme version 18.31


Label closed stale issues/PRs

This way they're easily identifiable for later review
Add a nudge to encourage contribution for stale issues.
Convert message text to multiline strings for ease of future maintenance
Aggregate related configuration for ease of comprehension and future maintenance

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 66.23%. Comparing base (8907a11) to head (361a2df).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1165      +/-   ##
==========================================
+ Coverage   65.76%   66.23%   +0.46%
==========================================
  Files         164      164
  Lines       13645    10582    -3063
==========================================
- Hits         8974     7009    -1965
+ Misses       4191     3090    -1101
- Partials      480      483       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Adding idea status value object

Closes #6 issue

Pull Request Test Coverage Report for Build 53

11 of 11 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 96.842%

Totals

Change from base Build 51:
0.4%

Covered Lines:
92

Relevant Lines:
95

💛  - Coveralls


How to fix SSMS 18

Are you seeing The query has been canceled because the estimated cost of this query?
Go into Tools > Options> Query Execution > SQL Server > Advanced
Change set query governor cost limit to 0 (unlimited)
MS in their infinite wisdom decided we need local SSMS governors so tight it kills 2 second queries.

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

ID: ef632046-6b35-8bb6-d3f7-9eb8a752d84e
Version Independent ID: 4e08e515-9ee3-7414-9683-639f740fef83
Content: SET QUERY_GOVERNOR_COST_LIMIT (Transact-SQL) - SQL Server
Content Source: docs/t-sql/statements/set-query-governor-cost-limit-transact-sql.md
Product: sql
Technology: t-sql
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

Note you will need to close and re-open SSMS.
That'll teach you to update a Microsoft product.

@dimmthewitted Thank you for the feedback.
The latest version of SSMS has the default setting set to 0:

Could this setting have been set to 2 by another process?

Closing this now, please comment below if there are further issues.


DHBW Timetable stopped on settings result sync range future changed

Done since we have now a loading screen for this.