Enable configuration for icons in folders

This PR enables the icon configuration on folders, multi-branch projects and organization folders to be accessible. This way one can customize the folder icon via jenkinsci/custom-folder-icon-plugin.
See https://github.com/jenkinsci/custom-folder-icon-plugin/issues/92 as well for details and use case.

Here the jenkinsci/custom-folder-icon-plugin is installed, by default there is only stockFolderIcon and metaDataActionFolderIcon available.
Example configuration:
folder('stock')

userContent('customFolderIcons/custom.png', streamFileFromWorkspace('custom.png'))
folder('custom') {
  icon {
    customFolderIcon {
      foldericon('custom.png')
    }
  }
}
folder('ionicon') {
  icon {
    ioniconFolderIcon {
      ionicon('jenkins')
    }
  }
}
folder('build-status') {
  icon {
      buildStatusFolderIcon()
  }
}

As for the failing test, I have no idea how to fix it if I'm honest other than removing the example. Any hints are highly appreciated.

@jamietanna Can you take a look please ?

Ping @jenkinsci/job-dsl-plugin-developers

@jamietanna Any update on this? Just wondering if there is anything I could do to get this merged.

Stack trace from failing test is:
Expected no exception to be thrown, but got 'javaposse.jobdsl.dsl.DslScriptException'
	at spock.lang.Specification.noExceptionThrown(Specification.java:118)
	at javaposse.jobdsl.dsl.doc.ExampleValidationSpec.test examples in #file(ExampleValidationSpec.groovy:32)
Caused by: javaposse.jobdsl.dsl.DslScriptException: (script, line 8) No signature of method: javaposse.jobdsl.dsl.helpers.icon.FolderIconContext.customFolderIcon() is applicable for argument types: (script$_run_closure1$_closure4$_closure5) values: [script$_run_closure1$_closure4$_closure5@78eced16]
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at javaposse.jobdsl.dsl.AbstractDslScriptLoader.runScriptEngine(AbstractDslScriptLoader.groovy:114)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at javaposse.jobdsl.dsl.AbstractDslScriptLoader.runScripts_closure1(AbstractDslScriptLoader.groovy:61)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at groovy.lang.Closure.call(Closure.java:414)
	at groovy.lang.Closure.call(Closure.java:430)
	at javaposse.jobdsl.dsl.AbstractDslScriptLoader.runScripts(AbstractDslScriptLoader.groovy:46)
	at javaposse.jobdsl.dsl.doc.ExampleValidationSpec.test examples in #file(ExampleValidationSpec.groovy:29)
Caused by: groovy.lang.MissingMethodException: No signature of method: javaposse.jobdsl.dsl.helpers.icon.FolderIconContext.customFolderIcon() is applicable for argument types: (script$_run_closure1$_closure4$_closure5) values: [script$_run_closure1$_closure4$_closure5@78eced16]
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at javaposse.jobdsl.dsl.AbstractExtensibleContext.methodMissing(AbstractExtensibleContext.groovy:19)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at script.run_closure1$_closure4(script:8)
	at script.run_closure1$_closure4(script)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at javaposse.jobdsl.dsl.ContextHelper.executeInContext(ContextHelper.groovy:16)
	at javaposse.jobdsl.dsl.AbstractFolder.icon(AbstractFolder.groovy:66)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at script.run_closure1(script:7)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at groovy.lang.Closure.call(Closure.java:414)
	at groovy.lang.Closure.call(Closure.java:430)
	at javaposse.jobdsl.dsl.JobParent.processItem(JobParent.groovy:238)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46)
	at groovy.lang.Script.invokeMethod(Script.java:80)
	at javaposse.jobdsl.dsl.JobParent.folder(JobParent.groovy:174)
	at script.run(script:6)
	at javaposse.jobdsl.dsl.AbstractDslScriptLoader.runScript(AbstractDslScriptLoader.groovy:138)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at javaposse.jobdsl.dsl.AbstractDslScriptLoader.runScriptEngine(AbstractDslScriptLoader.groovy:108)
	... 7 more

I'd wager that the custom icon plugin is not installed in the test instance and therefore the test script cannot be applied.
The problem is that I don't know how to fix this, a couple ideas:

make the plugin available on the test instance, but no other non-core plugins are installed, which is likely on purpose. This points to either:

having this plugin added in core (not likely and probably not desirable)
installing it in the build.gradle file (but it's likely not what the Job DSL plugin maintainers have in mind, they probably want to avoid pulling complexity from non-core plugins in their own)

update the custom folder icon plugin so that its configuration does not clash with that of the Folder plugin which is from the core and installed on all instances. I'm not sure this is the right option either, can the custom folder icon plugin overwrite settings from the Folder plugin? Was the Folder plugin planning for its configuration to be over-written? :thinking:

Unfortunately, I'm far from a Gradle pro and I didn't manage to tweak this project's build.gradle file to test my hypothesis :disappointed:

@quilicicf sums it up perfectly.

I'd wager that the custom icon plugin is not installed in the test instance and therefore the test script cannot be applied.

I do second this, however I yet have to find a way to change that.

make the plugin available on the test instance, but no other non-core plugins are installed, which is likely on purpose. This points to either:

having this plugin added in core (not likely and probably not desirable)
installing it in the build.gradle file (but it's likely not what the Job DSL plugin maintainers have in mind, they probably want to avoid pulling complexity from non-core plugins in their own)

I would prefer the 2nd option where my plugin is only pulled as a "test dependency" but should by no means be a required dependency of the job-dsl-plugin otherwise.

update the custom folder icon plugin so that its configuration does not clash with that of the Folder plugin which is from the core and installed on all instances. I'm not sure this is the right option either, can the custom folder icon plugin overwrite settings from the Folder plugin? Was the Folder plugin planning for its configuration to be over-written? 🤔

My plugin uses the intended way of extending the Folders plugin and provides additional functionality alongside its own configuration. There is no clash in any way. To elaborate further, the "icon" property of a folder is intended to be overwritten but this was not foreseen in the job-dsl-plugin implementation - which is exactly what this PR is trying to change.

Unfortunately, I'm far from a Gradle pro and I didn't manage to tweak this project's build.gradle file to test my hypothesis 😞
I'm in the same boat as you and since there is basically little to no documentation for the gradle build process of Jenkins plugins or other plugin projects using gradle to look at I desperately hope for @jamietanna to help me out here and get this PR merged.

It would be super nice if the Job DSL plugin allowed extensions like this indeed.
Let's wait for maintainers to answer then.

Apparently the plugin will switch to maven build (https://github.com/jenkinsci/job-dsl-plugin/pull/1265)

@jonesbusy I will look into this PR again once #1265 is merged ✌🏼

Thanks folks, sorry for the delay, but with the Maven changes in it may resolve the build issues 🤞🏽

@jamietanna I cannot get the ExampleValidationSpec test for the icon.groovy to work the way I want it to. I have no idea why that is and I'm giving up on it for now. Unless you can give me any pointer on what I'm missing, I simply can not put more time into it. I removed the example that uses the custom-folder-icon-plugin and only left the default example.
However I verified manually that everything is working just fine: Once the custom-folder-icon-plugin is installed I have the full selection of implementations available and all of them can be configured and do work just as described in my initial comment.
I would still love to see this merged eventually.

I have not reviewed this change thoroughly. At minimum it is missing @RequiresPlugin/@RequiresPlugins and the icon examples need to be restored.

@basil The icon property is provided by the Folders plugin and is not something introduced by the custom-folder-icon. So @RequiresPlugin needs to only be set to the Folders plugin, which is already the case.
For the example I tried everything that came to my mind over the course of now almost 6 month. I was unable to come up with any solution that does work other than disabling the test that fails because of it. As I already said, it would be great to have the examples included but unless someone comes up with an idea why it is not working and / or how to fix it there is nothing I can do.
The test setup with groovy, mocking via Spock and little to no docs / examples even drove me towards looking for a solution via ChatGPT, but it failed me as well. 🤷🏼

I took a closer look. It looks like FolderPropertiesContext and FolderIconContext are defined in the old-style DSL but extended by the Dynamic DSL. This is inconsistent, but since it is a preëxisting issue I will not insist that you fix it in this PR.
Since the Dynamic DSL is not available in job-dsl-core, the only way for you to test this is in job-dsl-plugin. Please add custom-folder-icon in test scope to job-dsl-plugin/pom.xml and then write tests for this in javaposse.jobdsl.plugin.ExecuteDslScriptsSpec. In this environment, the custom-folder-icon plugin will be loaded by JenkinsRule and will be available for the Dynamic DSL.
(No LLMs were consulted during the writing of this answer.)

@basil Thanks again for you help. As requested I added tests for every icon type we currently have, excluding the EmojiFolderIcon which I will add once the baseline is bumped to 2.387.1.

My latest commit is not showing in the PR. Any idea how to fix that 😕
https://github.com/strangelookingnerd/job-dsl-plugin/commit/b4987b1201badb9f62e666fdc0cf16a666c8f37d

which I will add once the baseline is bumped to 2.387.1.

#1288

Added a test for the EmojiFolderIcon as well 👍🏼

Released in 1.83.


Make ol.style.Style a @struct

And take into account that styles may be a style or an array of style.

Thanks for the explanations, please merge @fredj.

Thanks for the review


Version 0.2.9

remove keytype(::Tuple) due to https://github.com/JuliaLang/julia/pull/49179
resolve two ambiguities of BlockArrays.jl
remove an ambiguity resolver due to https://github.com/JuliaArrays/BlockArrays.jl/pull/410
move to Julia 1.11

Codecov Report
Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 46.19%. Comparing base (a8e4352) to head (16a4701).

Files with missing lines
Patch %
Lines

ext/PTYQoLBlockArraysExt.jl
0.00%
2 Missing :warning:

ext/PTYQoLInfiniteArraysExt.jl
0.00%
1 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (a8e4352) and HEAD (16a4701). Click for more details.
HEAD has 2 uploads less than BASE

Flag
BASE (a8e4352)
HEAD (16a4701)

3
1

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
- Coverage   52.01%   46.19%   -5.82%
==========================================
  Files          16       16
  Lines         373      368       -5
==========================================
- Hits          194      170      -24
- Misses        179      198      +19

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


grub.cfg not supported by Xen's pygrub

Version (k3OS / kernel)
k3os version v0.10.2
xen-utils-4.9
Architecture
x86_64
Describe the bug
I'm trying to boot K3OS with Xen using PyGrub. K3OS uses this grub stanza:
menuentry "k3OS Current" {
  search.fs_label K3OS_STATE root
  set sqfile=/k3os/system/kernel/current/kernel.squashfs
  loopback loop0 /$sqfile
  set root=($root)
  linux (loop0)/vmlinuz printk.devkmsg=on console=tty1 console=console
  initrd /k3os/system/kernel/current/initrd
}

Both search.fs_label and loopback aren't supported by PyGrub.
There's two routes to fix this:

Implement these features in PyGrub. (Will be a while until that makes it into all distros)
Stop using these features in K3OS.

What route do you prefer?
For 1: https://www.gnu.org/software/grub/manual/grub/html_node/search.html says search.fs_label is just an alias, so that should be a trivial fix.
For 2: The easy fix is not to compress the kernel with squashfs (just like you do for the 'previous' kernel), that removes the need for loopback. But I suspect there's a reason you did it this way (saving space?) which I don't know.
After these two fixes it seems to work fine (I worked around it by not using pygrub but hardcoding a kernel and ramdisk, so updates won't work.)
Actual behavior
Using <class 'grub.GrubConf.Grub2ConfigFile'> to parse /boot/grub/grub.cfg
WARNING:root:Unknown image directive search.fs_label
WARNING:root:Unknown image directive loopback

The "previous" grub entry is out of date, it will use a squashfs as well.


bulkai support midjourney v5.2

Could you elaborate this please? What exactly is not working from midjourney 5.2?

Could you elaborate this please? What exactly is not working from midjourney 5.2?

Sorry, I got it wrong, bulkai supports v5.2. In midjourney 5.2, Make Variations will change to vary(strong) and vary(subtle) after U1~U4 operations

I have merged this https://github.com/igolaizola/bulkai/pull/43
But I haven't tested it because I don't currently have an active midjourney subscription

I have merged this #43 But I haven't tested it because I don't currently have an active midjourney subscription

I tried it, no problem


hive ACID support

The hive compaction should be activated on one of the hive metastores. This requires distinction between the two hive metastores , to configure the hive.compactor.initiator.on on only one of the instance.

Properties linked to ACID support:
hive.support.concurrency – true
hive.enforce.bucketing – true (Not required as of Hive 2.0)
hive.exec.dynamic.partition.mode – nonstrict
hive.txn.manager – org.apache.hadoop.hive.ql.lockmgr.DbTxnManager
hive.compactor.initiator.on – true (for exactly one instance of the Thrift metastore service)
hive.compactor.worker.threads – a positive number on at least one instance of the Thrift metastore service

When trying to create a transactional table with "transactional"="true", the query fail with :
Error: Error while compiling statement: FAILED: LockException [Error 10280]: Error communicating with the metastore (state=42000,code=10280)

In the metastore logs we get :
ERROR [pool-11-thread-10:ProcessFunction@41] - Internal error processing open_txns
org.apache.hadoop.hive.metastore.api.MetaException: Unable to select from transaction database org.postgresql.util.PSQLException: ERROR: relation "next_txn_id" does not exist
[...]
INFO  [pool-11-thread-10:TxnHandler@3275] - Non-retryable error in openTxns(OpenTxnRequest(num_txns:1, user:tdp_user, hostname:master-03, agentInfo:Unknown)) : ERROR: relation "next_txn_id" does not exist
  Position: 23 (SQLState=42P01, ErrorCode=0)
[...]
ERROR [pool-11-thread-10:RetryingHMSHandler@201] - MetaException(message:Unable to select from transaction database org.postgresql.util.PSQLException: ERROR: relation "next_txn_id" does not exist

This seems to be linked to https://issues.apache.org/jira/browse/HIVE-22546, where there is problem with the metastore schema for the postgresql backend.
The transaction manager look for next_txn_id while the metastore have NEXT_TXN_ID .


Questions about i18next-http-backend and client-side only translations

Hey, I feel like I'm missing something huge:
I don't get how and when i18next-http-backend is doing something.
Since we always need a serverSideTranslations usage to retrieve translations, and the i18next instance is only being created when using serverSideTranslations, I have no idea when we could fetch translations on the client-side.
This relates to another question I'm asking myself:
Is there a way to create a i18next instance without using serverSideTranslations?
Like if a page only needs to be created on the client-side, how the i18next instance is supposed to be created?

Hey @LeonardDrs. Thanks for all your help recently, and I really appreciate that you have clearly taken a deep dive into the code. Let me answer your two questions:

I don't get how and when i18next-http-backend is doing something

I was actually just thinking this myself recently – since we're now treating translation data as props, and passing that off to NextJs, I think we can remove i18next-http-backend. In previous versions, we relied on it heavily inside getInitialProps, which is called on the client side upon route navigation.
There are some "nice to have" features that i18next-http-backend provides, like detected and adding missing translations, but we should probably just kick that out to userland, as people can always pass anything into use.

if a page only needs to be created on the client-side, how the i18next instance is supposed to be created?

Not sure I get your meaning. An i18next instance will be created by this line, both in server contexts and in client contexts. Have I misunderstood your question?

I'm glad I can be helpful!
I agree to your first point, but it could be related to the second question:

Not sure I get your meaning. An i18next instance will be created by this line, both in server contexts and in client contexts. Have I misunderstood your question?

Yeah but we only reach this line if props?.pageProps?._nextI18Next is true.
Which mean that if we don't use serverSideTranslations - like when the user wants to not use getServerSideProps / getStaticProps - we never create the i18next instance.
In which case the user would instanciate i18next himself and i18next-http-backend would provide useful. But all could be done in the userland.
So my question would be:
How should the user instanciate i18next himself in such case?

Why would a user not want to use one of NextJs' data fetching methods? That is the main way that next-i18next is proposing to handle translations.
Can you give an example use case?

I agree with you and I have no such example. I may have been over-thinking.

Do we agree to not lazy load the translations and have them always fetched in the serverSideTranslations of the page, even if the user may never load the modal?
I think it's perfectly fine, just wanted to clarify.

You are now getting into more nuanced problems with localisation, @LeonardDrs. The short answer is that it's a somewhat unsolved problem, and in general the solution will be to treat our translations more like code, than content, and treeshake/bundle them with tools like webpack.
For now, the next-i18next@beta functionality is about as good as it gets, in terms of industry standards.

Yeah I agree, thanks a lot for your time and thoughts!
Shall we close this issue or do you want to use it to keep track of i18next-http-backend modifications?

@LeonardDrs I've addressed this in #971. Also reduces the bundle size of next-i18next by ~10%. Thanks!

My pleasure, thank you for your awesome work!

Oups, was a bit too hasty. Will let the merge close this one


Investigate changes needed for Capella in Web3Signer

For Capella CL updates, there’s new block bodies and blinded block bodies to cater for sending bls_to_execution changes and withdrawals.

Identify changes for Web3Signer in terms of withdrawl signing requests (New API or modifications to existing API?).
Coordinate with EL team (such as Teku) to finalize the changes
Create new issues if required.

might be a duplicate or related to https://github.com/ConsenSys/web3signer/issues/673


Multiroot Workspaces per folder profile

It would be nice to be able to apply different profiles on per folder basis for multi-root workspaces.
For example I work on a project that has backend in Python and frontend in Typescript. Thus I use different profiles for each part of the project, however this means I have to open two VSCode instances at the same time, with different profiles applied. And also VSCode treats this as two different workspaces even though "logically" it's same project.

If I understand, you want to open a MR workspace and have two profiles applied for that?

Yes, exactly.

I do not think it is trivial to support and not according to the current design of how workspaces and profiles work. It is designed such a way that a workspace can be associated to a single profile.

It's a pity.


Threshold an object checks its properties

String properties still get matched exactly.
This allows us to start using thresholds again. (Without this we'd have to update the tests every time the weights changed)

This is one way to close out https://github.com/paritytech/parachains-integration-tests/issues/93 but nacho says he's going to implement it a different way.

This is one way to close out #93 but nacho says he's going to implement it a different way.

I've been analysing how to do in a different way and it is not trivial. I think this is a good solution at least for now. Merging


Verify windows binaries

I have not verified that the windows binaries (from travis-ci) actually work, since I don't have a windows machine.

Tried out the windows release with a Falcon 8 v1.  It runs fine and says it wrote bytes, but nothing appears to have changed after resetting.

Does not even run for me.


program-runtime: double program cache size

The cache is currently getting thrashed and programs are getting reloaded pretty much at every single slot. Double the cache size, which makes reloading happen only due to random eviction sometimes picking a popular entry.
The JIT code size with the new cache size is about 800MB.
This change reduces JIT time 15x.
Left is with PR, right is master.

I'm seeing ~100ms per slot spent filtering/replenishing program cache over the last 7 days on mainnet.

Yep one odd thing I noticed is that our devboxes and canaries have about 2x worse mean program cache perf than mnb. I don't know if it's because we've got potatoes compared to mnb nodes, or if we have an actual regression in master

or if we have an actual regression in master

Can you run a v2.0 node on your devbox for comparison?

I don't know if it's because we've got potatoes compared to mnb nodes, or if we have an actual regression in master

Sample size of 1, but mds3Df1ieBonG2qS8ZoKTqshq5MgTUNfZgc78cjiCdq is running v2.1.1 on mainnet and looks significantly worse than cluster mean


Followed tutorial so I could make a pine forest, but crashing on world load.

I have been practicing modding minecraft, and I needed to make a pine forest biome (I am not copying, it is literally just a weird coincidence we have the same wood type), but my game crashes whenever I try to either load into, or generate, a world. I have no idea why. I will upload my crash report and pine_forest.json files. @Kaupenjoe do you have any idea why?
pine_forest.json
crash-2024-01-17_12.40.25-server.txt

Had same error too, turns out "feature cycle" is the way vanilla registers features. If your mod registers things in a different order than vanilla, it will crash.

How would I fix this?

For example, if ores depend on caves being loaded, and your mod registers the ores before the cave, it will crash.


Add Typescript Vite Config Example

Just ran into this problem and it wasted a lot of time. Hopefully this helps others save some time!

Instead of adding a specific example for TypeScript, it's better to add information about vite.config.js being the default value, anything else needs to be specified in the configPath, e.g. configPath: "vite.config.ts".
Let me know if this solves your concern.

Thanks for the quick reply @pzmosquito!
I'm not sure I'm understanding. It would be nice to make it very obvious that the default value does not support the typescript version of the vite config file and the user needs to then specify the path. Maybe you are saying the same thing but could you provide a more clear example of what you'd like to see and I can fix up this PR.
Thanks!

updated README file with more description (f2d5719ed17754d712778398b96f60e8ae830680)


Thumbs up icon on facebook does not transfer over

Does not show up correctly.

It could show as a thumbnail, if Facebook wouldn't place some weird extensions in the URL.
I'll see what I can do about it

Just reporting in. Thanks for making this!

I'm currently waiting for Travis check and merging in last fixes, I'm not sure if this works with all of the stickers, but surely with the "thumbs up".

@talormanda Alright, it should work now.

@Bjornskjald do i have to redownload the package and install?

If you downloaded the .zip, you should be able to just replace the createEmbed.js file in lib folder, but redownloading is the most correct way to upgrade in the case of bigger updates. (existing config.json should work across all 2.x.x versions)

@Bjornskjald Just tested on my raspberry pi, works!


install deps for non OSX platforms too

currently we only install prerequisite when running on OSX, we should do the same for Windows and Linux too https://github.com/jenkins-x/jenkins-x-platform/blob/master/Makefile#L16

we do (some) of this now, but not all.


mongodb30: update to 3.0.12

Updates mongodb to 3.0.12 and mongo-tools to 3.0.12.
mongo-tools install.sh was updated as per https://jira.mongodb.org/browse/TOOLS-1151. This change should affect the 3.2.x branch when mongo-tools gets its next release.
mongo-tools appears to build with the new -ldflags, but I didn't want to make any drastic changes.

Thanks for your contribution to Homebrew!  You rock!
For future reference the preferred commit message format for simple version updates is mongodb30 3.0.12. This format is detailed in the linked Contributing guidelines. Thanks!


License

There are multiple Creative Commons licenses and multiple CC licenses in the 4.0 version.
Here they are: https://creativecommons.org/licenses/.
Most of them are non-free and they are widely different. "CC 4.0" licensed means absolutely nothing.
Still, the purpose of this repository is to have them under the Creative Commons Attribution 4.0 International Public License or, for short, CC BY-4.0 (notice the "BY"). I know this because of the package.json file specifying "CC-BY-4.0": this is literally the only clue I can see to which license we are talking about.
I suggest updating the readme to reflect this. Otherwise, it's very confusing.
Before fixing this, I suggest notifying all contributors to make sure they agree: this should be fairly easy as there are only 6 of them.
Thanks!

This is especially confusing since on the website there is a contradictory statement: https://boxicons.com/usage/#license
As you can see, CC 4.0 links to CC 4.0 BY, but it says just below that attribution isn't required, which is in contradiction with the CC 4.0 BY license, where the BY means that attribution is required.

Yeah, and also it is unclear what kind of attribution is required for what kind of use. Is it enough to add a comment in the code where the icon is used saying something like Icon by boxicons.com under cc by 4.0? Or should one attribute in the footer of the website? What if there are different icon sets used, how attribute only specific icons? Etc...

Note: they cannot add requirements on the specific way of providing attribution because CC BY 4.0 does not allow adding restrictions (only exceptions: additional permissions).
Any attribution in compliacne with CC BY 4.0 will be fine.


Latest release documentation has start_aggtrade_futures_socket method, but download via pip has not in python-binance 0.7.9 latest release

I've downloaded via pip python-binance 0.7.9.
In documentation is says, it has methood start_aggtrade_futures_socket.
See this link
https://python-binance.readthedocs.io/en/latest/binance.html#binance.websockets.BinanceSocketManager.start_aggtrade_futures_socket
But in downloaded python-binance package, it doesn't have this method in binance.websockets file.
Can anyone help me out why this is happening?

@JayDarji There are 2 versions of documentation.
You see the latest version it is for master branch.
If you want to see the stable version (for last release 0.7.9) you shold to switch it in left bottom corner.


how would i change the scene or add more cars ?

I want to have a game scene on the city road environment with buildings and other vehicles around, would someone guide me how to work on it?

@helxsz were you able to create a new game scene and other vehicles?

This sounds fun.  Please let us know how this progresses.


Handle EndOfConversation(EoC Activity) in Skills in Bot Composer

@dmvtech Can you please let me know the behaviour for EndOfConversation activity in Root and skill bots?
Let say if EoC Activity hits the root bot, we close the connection in the root bot, but the skill will be open and so instances will be running right? Wont that cause a problem?

EoC Activity is endOfConversation Activity. We are developing a audio bot, which is been integrated with third party service, so whenever the caller disconnect the call we get EoC Activity, but when the connection is in skill, this activity wont reach the skill bot. But as discussed earlier for events the control always goes through the root bot, though we have bypassed the EoC Activity in root bot, the control doesnt reach the skill bot, rather than that it will be treated as endOfConversation triggered to the root bot.
If that happens, I assume that the skill bot instances will be open as autoEndDialog is false and occupying the memory space increasing CPU load and which in turn can lead to 504 timeout issues. I am not really sure about the understanding but assumes it happens in this way, can you please guide me on it.

@dmvtech, Hi Dana, if we want to discuss it over an meeting, if you can share your email and prefereed time, I can book a slot. I am in IST zone and so till 11.00PM IST works for me. Thanks in advance.

As this is not possible in Composer, switching this over to a feature request.

Describe the solution you'd like
When there is a Root bot calling a skill; when the Root bot receives a EndOfConversation activity, then that should be forwarded to the skill and the skill should also be able to handle that same activity in it's own EndOfConversation activity handler.
Additional context
Sample activity being sent to the Root bot:
[Activity
    Type = endOfConversation
    Code = userCancelled
	Text = "Testing"
]


UIPER-125: Fix tests

https://folio-org.atlassian.net/browse/UIPER-125

Thanks for dealing with this.


Frozen applications which (indirectly!) depend on dask fail due to code that runs on import

What happened:
Any frozen application created that (indirectly!) depends on Dask will fail on start.
Indirectly because for example by depending on skimage, you also depend on Dask, without even knowing it.
I'm not the first to run into this problem: https://stackoverflow.com/questions/57057336/dask-pyinstaller-fails
In particular this is the offending code: https://github.com/dask/dask/blob/master/dask/config.py#L578-L589
def _initialize():
    fn = os.path.join(os.path.dirname(__file__), "dask.yaml")
    ensure_file(source=fn)

    with open(fn) as f:
        _defaults = yaml.safe_load(f)

    update_defaults(_defaults)

_initialize()  # <-- I/O code runs on import

The more general design flaw here is that you should never run code on import in a library! It's hostile to users since you can never take into account all use cases of your library.
In this specific case import time (which almost always equates to application startup time) is also slowed down significantly because there are I/O operations happening.
Example stacktrace of a pyinstaller-frozen application importing skimage:
  File "d:\a\1\s\.venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 623, in exec_module
  File "lib\site-packages\skimage\__init__.py", line 167, in <module>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "d:\a\1\s\.venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 623, in exec_module
  File "lib\site-packages\skimage\util\__init__.py", line 6, in <module>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "d:\a\1\s\.venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 623, in exec_module
  File "lib\site-packages\skimage\util\apply_parallel.py", line 8, in <module>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "d:\a\1\s\.venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 623, in exec_module
  File "lib\site-packages\dask\__init__.py", line 1, in <module>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "d:\a\1\s\.venv\lib\site-packages\PyInstaller\loader\pyimod03_importers.py", line 623, in exec_module
  File "lib\site-packages\dask\config.py", line 589, in <module>
  File "lib\site-packages\dask\config.py", line 582, in _initialize
FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Program Files\\XXXXXXXXXXX\\dask\\dask.yaml'

What you expected to happen:
Nothing should happen when Dask is imported!
Minimal Complete Verifiable Example:
Freeze a python application that depends on Dask. Run it. See the linked SO question for a very brief verifiable example.

Thank you for bringing this up. Do you have a proposal for how dask might handle configuration without doing anything on import?

Historically we wrote a commented out config file on import so that users
could inspect that file, uncomment various lines, and then change them as
needed.
In practice I'm not sure how much this is used today.  Config files tend to
be quite large, and somewhat hard to uncomment and modify due to nesting.
Personally I find myself copying snippets from doc pages or stack overflow
answers, removing the commented text and overwriting it with the
small snippet that I copied over.  I was probably the strongest proponent
for copying in commented-out config files.  I'd be open to reversing that
position.
cc @jcrist who I think held the opposing view somewhat strongly.
On Wed, Sep 16, 2020 at 8:22 AM Julia Signell<EMAIL_ADDRESS>wrote:

Thank you for bringing this up. Do you have a proposal for how dask might
handle configuration without doing anything on import?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/6634#issuecomment-693478411, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTFJ6ZEPBW5R6RNQEWDSGDJZXANCNFSM4RLH4MAA
.

cc @jcrist who I think held the opposing view somewhat strongly.

Yeah, I'd be quite happy for the automatic-writing-of-commented-out-config-files stuff to go away. I don't think it's that useful, and it can be quite unexpected (and may lead to surprising issues like this). For example, I recently ran into issues when running in an execution environment with very slow disk write access. Importing dask would attempt to write to disk, leading to ~15 s worker setup.

It's an easy change if we want to make it
https://github.com/dask/dask/pull/6647
On Wed, Sep 16, 2020 at 9:24 AM Jim Crist-Harif<EMAIL_ADDRESS>wrote:

cc @jcrist https://github.com/jcrist who I think held the opposing view
somewhat strongly.
Yeah, I'd be quite happy for the
automatic-writing-of-commented-out-config-files stuff to go away. I don't
think it's that useful, and it can be quite unexpected (and may lead to
surprising issues like this). For example, I recently ran into issues when
running in an execution environment with very slow disk write access.
Importing dask would attempt to write to disk, leading to ~15 s worker
setup.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/6634#issuecomment-693516946, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTGPPLRAX2O6SFLC4HLSGDRFHANCNFSM4RLH4MAA
.

Well, you could start by not creating the file automatically and only checking for existence of the file instead. That would avoid most of the trouble.
As a next step, you could provide an explicit function for users to call to initialize config instead.
Alternatively you could initialize on demand within other library function calls but that is also not without drawbacks..


Better panning

Hello and thank you for your awesome work with Eto.OpenTK. I use it alot.
I found your implementation of panning to be very sluggish. Especially considering zooming works very well. I made the following improvements to the dragHandler function in the TestViewport class:
float new_X = (ovpSettings.cameraPosition.X - (((float)e.Location.X - x_orig) * ovpSettings.zoomFactor));
float new_Y = (ovpSettings.cameraPosition.Y + (((float)e.Location.Y - y_orig) * ovpSettings.zoomFactor));
ovpSettings.cameraPosition = new PointF(new_X, new_Y);
x_orig = e.Location.X;
y_orig = e.Location.Y;

Simply exchanging the arbitray scaling factor in new_X and new_Y for ovpSettings.zoomFactor and updating x_orig and y_orig gives panning a feeling of moving a surface with the mouse. Much more pleasant!
Thank you

This works nicely - I have it implemented in my fork of Eto.OpenTK and would support this change in upstream.


new endpoint for cover crops api for thumbnails array

this is currently not needed, but instead is being moved to an issue with the species-selector api.
We would like to add thumbnail / family / group data to the crops object in species selector, that is synced with the cover crops api during broadcasting.


Data preparation

hmm, i really didn't get why i got this error
"File "./dataprep.py", line 173, in
raise ValueError('Target directory does not exist.')"
i don't know which part should be update for the save_path, anyone can help?
Thanks in advance..

./dataprep.py --save_path data --download --user USERNAME --password PASSWORD
ok, i got this one, data should be replace with the path, but i got another issue, is about Username/Password Authentication Failed


test: Use byte literals for Python3 compatibility

Because the stream is opened in binary mode. On Python3 that requires the replace to also operate in binary mode.

Cool!
@swift-ci smoke test and merge

@swift-ci smoke test Linux

@CodaFi the linux tests tests failed but I don't know how this caused it. The line related to this test says: 00:15:13 PASS: Swift(linux-x86_64) :: Syntax/tokens_unknown_and_invalid.swift (8440 of 13079).
Suggestions?

@swift-ci please test Windows platform

It’s not your failure.


SPARKC-405: B1.6

Throws an exception when trying to do a Spark(lexical) comparison on a TimeUUID, but allows comparisons if C* handles the entire comparison(Compared based on time).

Build against Scala 2.10 finished with success

Build against Scala 2.11 finished with failure

Build against Scala 2.10 finished with success

Build against Scala 2.11 finished with success

Build against Scala 2.10 finished with success

Build against Scala 2.11 finished with success

+1


Added BeardScript

Thanks for this. Don't be alarmed if you get a notification about something failing - the CI/CD is having trouble with PRs coming from forks and I need to find time to fix it. Your profile will still appear on the site within a few minutes of the merge

Excellent! Thanks for making this.


Syntax highlighting in request output breaks after a truncated request

If the response from an HTTP request is longer than the configured max, it will be trunctcated in the httpac - Request window with the ... (xxx characters more) message. This messes syntax highlighting of the rest of the request output:

I suspect this is caused because the returned JSON is not properly closed which may be tricky to handle, so I suspect there may be no easy fix, but wanted to mention it just in case. Maybe there is an option to not do syntax highlighting for truncated entries? Or maybe there are other workarounds? For now, I just increased the max length to 4K, which still may not work in some cases. Not sure if there is a better way.

fixed with next release

You rock!!!


Example pages

This PR:
Adds examples page(s) for showing combined components
Adds examples gulp task that copies files and wraps them in a template
Updates dev, review and watch tasks.
Example page url: http://govuk-frontend-review-pr-148.herokuapp.com/examples/example-form.html

Can we create govuk-bold-12 if we need it, rather than use the next mixin up?


Implement put and putdata methods in PyFerret

Reported by karl smith on 9 Mar 2011 20:02 UTC
put uses a cdms2 AbstractVariable and calls putdata
putdata uses a dictionary of values
should compliment getdata and get
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1808

Modified by karl.smith on 9 Mar 2011 20:02 UTC

Modified by karl.smith on 9 Mar 2011 20:06 UTC

Modified by karl.smith on 30 Mar 2011 18:17 UTC


FIXED: #1492, should not see or install unlisted packages

:shipit:

Copying my comment from the issue:
I think the desired behavior here should be the same as with NuGet.exe:

if no version is passed in, you the latest that's not unlisted
if a version is passed in, honor it regardless of whether it's listed or unlisted

Is that how your change works? Looking at the code, I'm not so sure.

current code change will not look from unlisted package.
tried with Nuget.exe, it won`t list any unlisted package, but do allow user to install package that is "unlisted"
updating logic to do similar behavior. will have code update soon.

@davidebbo sent out another PR to address your comment https://github.com/projectkudu/kudu/pull/1494, please review


Feat/rename subdomain

This is my first PR, so expect there to be a lot of suggestions. My google searches looked something like rust integers so that's where we're at right now 😆

No error on new subdomain name the same as old subdomain name.
Interactive, y/n to proceed with rename. Would ideally have more specific messaging around what scripts will be modified.
No existing subdomain command tests. I need some help to get that started if that's something we should add.
Second commit is correcting for subdomain availability api response. Not exactly related, but not unrelated either.

@nprogers - i'm assuming you used your work email to commit these, could you add your work email as a valid email address for your account so that the commits are properly attributed to your account? right now they are showing up as anonymous commits
here is info on how to do that

this looks good - just need to add that additional messaging about moving. as for tests - we need a solution to mock out API calls before we could test this reasonably i think.

re: gitignore - i could not care less


Cannot find name 'require' after upgrading to cli1.0.0 and Angular4

Bug Report or Feature Request (mark with an x)
- [x] bug report
- [ ] feature request

Versions.
@angular/cli: 1.0.0
node: 7.7.1
os: darwin x64
@angular/common: 4.0.0
@angular/compiler: 4.0.0
@angular/core: 4.0.0
@angular/forms: 4.0.0
@angular/http: 4.0.0
@angular/material: 2.0.0-beta.2
@angular/platform-browser: 4.0.0
@angular/platform-browser-dynamic: 4.0.0
@angular/router: 4.0.0
@angular/cli: 1.0.0
@angular/compiler-cli: 4.0.0
Repro steps.
ng new newapp
cd newapp
npm install chart.js --save
echo "export const { Chart } = require('chart.js');" >> src/app/chart.loader.ts
ng serve

The log given by the failure.
ERROR in /Users/xgwang/Workspace/playground/newapp/src/app/chart.loader.ts (1,26): Cannot find name 'require'.
Desired functionality.
In previous version it should work.
Clearly, in<EMAIL_ADDRESS>there is declare var require: NodeRequire;
But I don't understand why it does not compile.

@xg-wang I had the same error with firebase and the following update worked for me.
// const firebase = require('firebase');
import * as firebase from 'firebase';

@demirk4n Thanks, that works. Just confused why require can't do here.

add
"types": [
  "node"
]

into 'src/tsconfig.app.json'

No longer helps with 1.1.1

Doesn't seem to work in 1.1.3 either.

Setting this in tsconfig.json wont help because it's for the ide you use, the config file actually used for compilation is src/tsconfig.app.json. Putting
"types": [
      "node"
    ]

there solves the problem for me.

SHIT! ANGULAR IS SHIT

please someone help me resolve when I try to install crypto.js. This error comes
ERROR in /home/gajal/loktra/lms/src/app/login/login.component.ts (117,20): Cannot find name 'require'.
ERROR in /home/gajal/loktra/lms/src/app/login/login.component.ts (118,18): Cannot find name 'require'.


Re-instate "global" window-hiding-location (non-per-monitor) as a configuration option

So, my monitor layout is … pretty incompatible with the new(-ish) layout constraints as of I-think-around-0.14-ish.
Current layout:

(photo)

I'd like the previous behaviour to return as an option - that is, when enabled, Aerospace would use a single corner of a single monitor for all minimized windows.
This would result in the re-appearance of bugs such as #149 that the per-monitor "stash" is intended to bypass, when the option is enabled - for me, that's an acceptable trade-off, as Aerospace is freaking awesome, but also makes a huge portion of my display-space unusable since the change. 😩
In my setup, for example, the ideal behaviour would be Aerospace noticing that there's no monitors to the bottom-left of the leftmost side, and utilizing that corner as the "stash."
Yes, I'm aware I'm an outlier; I present this more as a supporting argument that this is worth at least retaining as an option. (In particular, even if you're a little less insane than me, one of the classic multi-monitor favourites - the H shape, i.e. ▐⧯▌ - still includes a centered monitor with no "empty" bottom-corner. )=)

System details
(Full AllRez output: gist)
$ aerospace --version
aerospace CLI client version: 0.15.2-Beta b6cf82771f245ab7349a93baf8709e171537ff58
AeroSpace.app server version: 0.15.2-Beta b6cf82771f245ab7349a93baf8709e171537ff58

$ system_profiler SPSoftwareDataType SPHardwareDataType
Software:

    System Software Overview:

      System Version: macOS 14.6.1 (23G93)
      Kernel Version: Darwin 23.6.0
      Boot Volume: Ime's HD
      Boot Mode: Normal
      Computer Name: Ime-the-MacPro7,1
      User Name: ELLIOTTCABLE (ec)
      Secure Virtual Memory: Enabled
      System Integrity Protection: Disabled
      Time since boot: 39 days, 1 hour, 17 minutes

Hardware:

    Hardware Overview:

      Model Name: Mac Pro
      Model Identifier: MacPro7,1
      Enclosure: Rack
      Processor Name: 12-Core Intel Xeon W
      Processor Speed: 3.3 GHz
      Number of Processors: 1
      Total Number of Cores: 12
      L2 Cache (per Core): 1 MB
      L3 Cache: 19.3 MB
      Hyper-Threading Technology: Enabled
      Memory: 48 GB
      System Firmware Version: 2<IP_ADDRESS>.0 (iBridge: 21.16.6074.0.0,0)
      OS Loader Version: 580.140.1~8
      Activation Lock Status: Enabled

$ system_profiler SPDisplaysDataType
2024-11-05 12:56:16.752 system_profiler[83706:91652599] Device PreExisted [0000000100000f3b] AMD Radeon PRO W6800X Duo
2024-11-05 12:56:16.753 system_profiler[83706:91652599] Device PreExisted [0000000100000f39] AMD Radeon PRO W6800X Duo
Graphics/Displays:

    AMD Radeon PRO W6800X Duo (Slot 1, GPU 1):

      Chipset Model: AMD Radeon PRO W6800X Duo
      Type: GPU
      Bus: PCIe
      Slot: Slot-1
      PCIe Lane Width: x16
      VRAM (Total): 32 GB
      Vendor: AMD (0x1002)
      Device ID: 0x73ab
      Revision ID: 0x0000
      ROM Revision: 113-D4171X-436
      VBIOS Version: 113-D417A1DXL-021
      Option ROM Version: 113-D417A1DXL-021
      EFI Driver Version: 01.01.270
      Metal Support: Metal 3
      GPU Number: 1
      GPU Peer Group:<PHONE_NUMBER>823197077
      GPU Peer Index: 0
      Infinity Fabric Link: Yes
      Displays:
        Pro Display XDR:
          Display Type: 2D backlit LCD
          Resolution: 6016 x 3384 Retina 6K
          Framebuffer Depth: 30-Bit Color (ARGB2101010)
          Display Serial Number: C02C708XML9V
          Display Firmware Version: 4.2.37
          Mirror: Off
          Online: Yes
          Automatically Adjust Brightness: No

    AMD Radeon PRO W6800X Duo (Slot 1, GPU 2):

      Chipset Model: AMD Radeon PRO W6800X Duo
      Type: GPU
      Bus: PCIe
      Slot: Slot-1
      PCIe Lane Width: x16
      VRAM (Total): 32 GB
      Vendor: AMD (0x1002)
      Device ID: 0x73ab
      Revision ID: 0x0000
      ROM Revision: 113-D4171X-436
      VBIOS Version: 113-D417A1DXL-021
      Option ROM Version: 113-D417A1DXL-021
      EFI Driver Version: 01.01.270
      Metal Support: Metal 3
      GPU Number: 2
      GPU Peer Group:<PHONE_NUMBER>823197077
      GPU Peer Index: 1
      Infinity Fabric Link: Yes
      Displays:
        U13NA:
          Resolution: 2560 x 1600
          UI Looks like: 1280 x 800 @ 60.00Hz
          Framebuffer Depth: 30-Bit Color (ARGB2101010)
          Display Serial Number: 1
          Mirror: Off
          Online: Yes
          Rotation: 180
          Connection Type: Thunderbolt/DisplayPort
        Pro Display XDR:
          Display Type: 2D backlit LCD
          Resolution: 6016 x 3384 Retina 6K
          Framebuffer Depth: 30-Bit Color (ARGB2101010)
          Display Serial Number: C02C40A8ML9W
          Display Firmware Version: 4.2.37
          Mirror: Off
          Online: Yes
          Automatically Adjust Brightness: No
        Pro Display XDR:
          Display Type: 2D backlit LCD
          Resolution: 6016 x 3384 Retina 6K
          Framebuffer Depth: 30-Bit Color (ARGB2101010)
          Display Serial Number: C02C70AKML9V
          Display Firmware Version: 4.2.37
          Main Display: Yes
          Mirror: Off
          Online: Yes
          Automatically Adjust Brightness: No
        Wisecoco:
          Resolution: 1100 x 3840
          UI Looks like: 550 x 1920 @ 60.00Hz
          Framebuffer Depth: 30-Bit Color (ARGB2101010)
          Mirror: Off
          Online: Yes
          Rotation: 270
          Adapter Type: DVI or HDMI
          Adapter Firmware Version: 2.19

$ system_profiler SPThunderboltDataType
Thunderbolt/USB4:

    Thunderbolt Bus 3:

      Vendor Name: Apple Inc.
      Device Name: Mac Pro
      UID: 0x0000597E6872A903
      Route String: 0
      Firmware Version: 63.3
      Domain UUID: 25C98C7C-4031-CF51-82D3-348175FF7A13
      Port:
          Status: No device connected
          Link Status: 0x7
          Speed: Up to 40 Gb/s x1
          Current Link Width: 0x1
          Receptacle: 8
          Link Controller Firmware Version: 1.43.0
      Port:
          Status: No device connected
          Link Status: 0x7
          Speed: Up to 40 Gb/s x1
          Current Link Width: 0x1
          Receptacle: 7
          Link Controller Firmware Version: 1.43.0

    Thunderbolt Bus 2:

      Vendor Name: Apple Inc.
      Device Name: Mac Pro
      UID: 0x0000597E6872A902
      Route String: 0
      Firmware Version: 63.3
      Domain UUID: C7A4163E-9331-C851-8352-08A5925090B2
      Port:
          Status: Device connected
          Link Status: 0x2
          Speed: Up to 40 Gb/s x1
          Current Link Width: 0x2
          Receptacle: 6
          Link Controller Firmware Version: 1.43.0
      Port:
          Status: Device connected
          Link Status: 0x2
          Speed: Up to 40 Gb/s x1
          Current Link Width: 0x2
          Receptacle: 5
          Link Controller Firmware Version: 1.43.0

        Element Hub:

          Vendor Name: CalDigit, Inc.
          Device Name: Element Hub
          Mode: Thunderbolt 3
          Device ID: 0x25
          Vendor ID: 0x3D
          Device Revision: 0x1
          UID: 0x8087A7369411D800
          Route String: 1
          Firmware Version: 36.1
          Port (Upstream):
              Status: Device connected
              Link Status: 0x2
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x2
          Port:
              Status: No device connected
              Link Status: 0x7
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x1
          Port:
              Status: Device connected
              Link Status: 0x2
              Speed: Up to 20 Gb/s x1
              Current Link Width: 0x2
          Port:
              Status: No device connected
              Link Status: 0x7
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x1

            Pro Display XDR:

              Vendor Name: Apple Inc.
              Device Name: Pro Display XDR
              Mode: Thunderbolt 3
              Device ID: 0x801F
              Vendor ID: 0x1
              Device Revision: 0x1
              UID: 0x000169A4A8208C00
              Route String: 501
              Firmware Version: 55.2
              Port (Upstream):
                  Status: Device connected
                  Link Status: 0x2
                  Speed: Up to 20 Gb/s x1
                  Current Link Width: 0x2
                  Link Controller Firmware Version: 1.41.0

        Thunderbolt 3 Option Card:

          Vendor Name: Universal Audio, Inc.
          Device Name: Thunderbolt 3 Option Card
          Mode: Thunderbolt 3
          Device ID: 0x6
          Vendor ID: 0x1176
          Device Revision: 0x1
          UID: 0x1176B7DD08FA5400
          Route String: 3
          Firmware Version: 29.3
          Port (Upstream):
              Status: Device connected
              Link Status: 0x2
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x2
              Link Controller Firmware Version: 0.33.0
          Port:
              Status: No device connected
              Link Status: 0x7
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x1
              Link Controller Firmware Version: 0.33.0

    Thunderbolt Bus 1:

      Vendor Name: Apple Inc.
      Device Name: Mac Pro
      UID: 0x0000597E6872A901
      Route String: 0
      Firmware Version: 63.3
      Domain UUID: D74A703A-6C3D-3358-A24B-9476CC35005B
      Port:
          Status: No device connected
          Link Status: 0x7
          Speed: Up to 40 Gb/s x1
          Current Link Width: 0x1
          Receptacle: 4
          Link Controller Firmware Version: 1.43.0
      Port:
          Status: Device connected
          Link Status: 0x2
          Speed: Up to 40 Gb/s x1
          Current Link Width: 0x2
          Receptacle: 3
          Link Controller Firmware Version: 1.43.0

        Element Hub:

          Vendor Name: CalDigit, Inc.
          Device Name: Element Hub
          Mode: Thunderbolt 3
          Device ID: 0x25
          Vendor ID: 0x3D
          Device Revision: 0x1
          UID: 0x8087C3A1A8020F00
          Route String: 3
          Firmware Version: 36.1
          Port (Upstream):
              Status: Device connected
              Link Status: 0x2
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x2
          Port:
              Status: No device connected
              Link Status: 0x7
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x1
          Port:
              Status: Device connected
              Link Status: 0x2
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x2
          Port:
              Status: Device connected
              Link Status: 0x2
              Speed: Up to 10 Gb/s x1
              Current Link Width: 0x1

            Pro Display XDR:

              Vendor Name: Apple Inc.
              Device Name: Pro Display XDR
              Mode: Thunderbolt 3
              Device ID: 0x801F
              Vendor ID: 0x1
              Device Revision: 0x1
              UID: 0x00015EE858B26200
              Route String: 503
              Firmware Version: 55.2
              Port (Upstream):
                  Status: Device connected
                  Link Status: 0x2
                  Speed: Up to 40 Gb/s x1
                  Current Link Width: 0x2
                  Link Controller Firmware Version: 1.41.0

            Apollo Twin:

              Vendor Name: Universal Audio, Inc.
              Device Name: Apollo Twin
              Mode: Thunderbolt
              Device ID: 0x2
              Vendor ID: 0x1176
              Device Revision: 0x1
              UID: 0x1176000200077260
              Route String: 703
              Firmware Version: 7.1
              Port (Upstream):
                  Status: Device connected
                  Link Status: 0x2
                  Speed: Up to 10 Gb/s x1
                  Port Micro Firmware Version: 2.0.7
                  Cable Firmware Version: 1.1.0 / 0.0.0

    Thunderbolt Bus 0:

      Vendor Name: Apple Inc.
      Device Name: Mac Pro
      UID: 0x0000597E6872A900
      Route String: 0
      Firmware Version: 63.3
      Domain UUID: 8C2F59B9-31F2-9656-803B-9D5DC6311AA3
      Port:
          Status: No device connected
          Link Status: 0x7
          Speed: Up to 40 Gb/s x1
          Current Link Width: 0x1
          Receptacle: 2
          Link Controller Firmware Version: 1.43.0
      Port:
          Status: Device connected
          Link Status: 0x2
          Speed: Up to 40 Gb/s x1
          Current Link Width: 0x2
          Receptacle: 1
          Link Controller Firmware Version: 1.43.0

        Pro Display XDR:

          Vendor Name: Apple Inc.
          Device Name: Pro Display XDR
          Mode: Thunderbolt 3
          Device ID: 0x801F
          Vendor ID: 0x1
          Device Revision: 0x1
          UID: 0x0001600540B16100
          Route String: 3
          Firmware Version: 55.2
          Port (Upstream):
              Status: Device connected
              Link Status: 0x2
              Speed: Up to 40 Gb/s x1
              Current Link Width: 0x2
              Link Controller Firmware Version: 1.41.0

Thanks, I appreciate the well written and clear issue.  One of the UX principles that I rely on is "don't provide configuration option that makes users choose between trade-offs". AeroSpace should work in the best possible way by default. That's why AeroSpace automatically chooses the most appropriate corner and doesn't ask users to configure corners manually.
Providing a configuration option to choose between "global hiding" and "local monitor hiding" is choosing between trade-offs, which I won't do.
Ok, so what is the best possible way AeroSpace can automatically behave? I think the way it behaves right now is the best possible way, since it forces users to reconsider their monitor arrangement.

Offtopic.
Well, there is a room for improvement - AeroSpace should show a notification / yellow dot in the status bar asking users to change their monitor configuration rather than forcing to read the guide, but it's an improvement for future versions.

Anticipating your next suggestion to use "global" approach when both corners are unavailable, IMO #149 is not an acceptable behavior. I still prefer to ask users to reconsider their monitor configuration, because the user will be happier in the long run.
Given the way AeroSpace implements workspaces, I think your monitor configuration is simply invalid, and I don't see a way to improve it.
Your concrete proposal to provide configuration option to choose between "global" and "local" hiding strategies is rejected => I close the issue. You're free to make other concrete proposals if you think that there is a way to support monitor configurations as yours.

Having said that, you have a workaround to run from sources with the following patch to return old behavior:
diff --git a/Sources/AppBundle/tree/MacWindow.swift b/Sources/AppBundle/tree/MacWindow.swift
index aaffca1c..f181ba55 100644
--- a/Sources/AppBundle/tree/MacWindow.swift
+++ b/Sources/AppBundle/tree/MacWindow.swift
@@ -116,21 +116,7 @@ final class MacWindow: Window, CustomStringConvertible {
             prevUnhiddenEmulationPositionRelativeToWorkspaceAssignedRect =
                 topLeftCorner - workspace.workspaceMonitor.rect.topLeftCorner
         }
-        let p: CGPoint
-        switch corner {
-            case .bottomLeftCorner:
-                guard let s = getSize() else { fallthrough }
-                // Zoom will jump off if you do one pixel offset https://github.com/nikitabobko/AeroSpace/issues/527
-                // todo this ad hoc won't be necessary once I implement optimization suggested by Zalim
-                let onePixelOffset = macApp.isZoom ? .zero : CGPoint(x: 1, y: -1)
-                p = nodeMonitor.visibleRect.bottomLeftCorner + onePixelOffset + CGPoint(x: -s.width, y: 0)
-            case .bottomRightCorner:
-                // Zoom will jump off if you do one pixel offset https://github.com/nikitabobko/AeroSpace/issues/527
-                // todo this ad hoc won't be necessary once I implement optimization suggested by Zalim
-                let onePixelOffset = macApp.isZoom ? .zero : CGPoint(x: 1, y: 1)
-                p = nodeMonitor.visibleRect.bottomRightCorner - onePixelOffset
-        }
-        _ = setTopLeftCorner(p)
+        _ = setTopLeftCorner(sortedMonitors.last!.rect.bottomRightCorner - CGPoint(x: 1, y: 1))
     }

     func unhideFromCorner() {

Yes, it comes with the cost of supporting your own fork and dealing with merge conflicts.
Please follow https://github.com/nikitabobko/AeroSpace/blob/main/dev-docs/development.md for the project setup. And you can use install-from-sources.sh in the repo root to install AeroSpace-SNAPSHOT as aerospace-dev cask.

The situation reminds me of xkcd.com/1172

That precise comic was on my mind while I wrote this, so I appreciate the vibes 😅

You're free to make other concrete proposals if you think that there is a way to support monitor configurations as yours.

Well, it's a last-ditch effort, but I do want to point out that other contributors' thoughts w.r.t. virtual displays tie in here. That is, there is a path forward for users like me that doesn't involve any runtime trade-offs; but it requires additional upfront setup, and requires such a configuration option.
So, basically, it's not precisely just a configuration option that leads to unacceptable tradeoffs; more precisely put, it's a configuration-option that can be (mis-?)used by some users to introduce negative experiences for themselves, if they're willing to turn it on, but not willing to put in the additional work to set it up "correctly."
That said, I do see how that difference is borderline pedantic, because your actual presumable objection is the result of "some users turn on an option, and have a bad time," and that still applies whether or not some other users will turn on that option and have a better time, so I'm really not sure how to sell that.

I'll try and think on better alternatives, but I doubt there'll be any within the constraints of macOS. Ugh, it's a microcosm of the whole thing, innit - trying to be a poweruser and get things done, but also remain within the blesséd land where productivity is possible; it's always a knife's-edge ...


Database handlers support sslmode=verify-full

verify-full is equivalent to VERIFY_IDENTITY as stated in the MySQL docs:

VERIFY_IDENTITY: Like VERIFY_CA, but additionally perform host name identity verification by checking the host name the client uses for connecting to the server against the identity in the certificate that the server sends to the client:

AC:

[ ] perform host name identity verification by checking the host name the client uses for connecting to the server against the identity in the certificate that the server sends to the client

Note - there was a request to get this fixed in https://github.com/cyberark/secretless-broker/issues/922

Today we briefly looked into what it would take to get this implemented. We noticed the two commented lines:
and wanted to validate whether simply uncommenting them would get this working e2e. It doesn't appear to have worked.
To try to get it working, I cloned the latest branch, uncommented these two lines, and ran ./bin/build_darwin.
I spun up a MySQL instance in a Docker container with:
docker run -d -p 3307:3306 --name mysql -e MYSQL_ROOT_PASSWORD=myrootpassword -e MYSQL_DATABASE=mydb -e MYSQL_USER=myuser -e MYSQL_PASSWORD=mypassword mysql:5

and copied the ca.pem, server-cert.pem, and server-key.pem files from /var/lib/mysql into my local dir.
Then I ran ./dist/darwin/amd64/secretless-broker -f secretless.yml where my secretless config was
version: "2"
services:
  test-verify-full:
    protocol: mysql
    listenOn: tcp://localhost:3306
    credentials:
      host: localhost
      port: 3307
      username: myuser
      password: mypassword
      sslmode: verify-full
      sslrootcert:
        from: file
        get: ca.pem
      sslcert:
        from: file
        get: server-cert.pem
      sslkey:
        from: file
        get: server-key.pem

I tried to run mysql -h <IP_ADDRESS> -P 3306 --ssl-mode=DISABLED, but I got the error
ERROR: 2000 (HY000): tls: either ServerName or InsecureSkipVerify must be specified in the tls.Config

Replacing verify-full with verify-ca got me into the DB.

@izgeri the reason your test failed is the host value is not present in the options parameter passed into NewDbSSLMode.
I've tested by hard coding the hostname at ssl.go#L62 to my MySQL hostname. That works - no error, and the connection is encrypted (verified by packet dump).
I also tested the hostname verification by changing host to an alias that doesn't match the name in the SSL certificate, and got error:
ERROR 2000 (HY000): x509: certificate is valid for <good hostname>, not <bad hostname>

@porjo Keeping my comment from here in mind about master vs latest branch, we may not be able to get this fixed up very quickly in the new refactor but we are accepting PRs for this release and the new one as well :)


Add option for web container to extend csp

Apps such as Meet and Konnect set strict csp that disallow embedding it from other domains.
The web container could extend these to allow embedding from a domain that is specified through an environment variable.
https://caddyserver.com/v1/docs/header

https://stash.kopano.io/projects/KGOL/repos/kweb/browse/snippets.d/60-kopano-staticpwa-csp.cfg


Anyway to reverse which way you swipe the gallery?

Is there a way to make the order of the gallery swipe to the right instead of the left ? So the order of the gallery would by default go backwards but the listview wouldn't be out of order for arabic books.
Thanks

Yes. You just need to provide the elements in a reverse order.
for example, if you are using this:
// Set up PhotoSwipe with all anchor tags in the Gallery container
document.addEventListener('DOMContentLoaded', function(){
var myPhotoSwipe = Code.PhotoSwipe.attach( window.document.querySelectorAll('#Gallery a'), { enableMouseWheel: false , enableKeyboard: false } );

}, false);
use this:
// Set up PhotoSwipe with all anchor tags in the Gallery container
document.addEventListener('DOMContentLoaded', function(){
var myPhotoSwipe = Code.PhotoSwipe.attach( $('#Gallery a').get().reverse(), { enableMouseWheel: false , enableKeyboard: false } );

}, false);
(I've used jQuery to make it easier).


Add trace links to the troubleshooting panel.

Korrel8r now has support for the "trace" domain, reading trace information from tempo.
Add support for translating trace queries to/from console trace search URLs.

/assign @shwetaap


KeyError when Darksky API call fails in units()

Home Assistant release with the issue: 86.4
Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Component/platform: Darksky
Description of problem:
If the API call to Darksky fails, the def units(self): fails with a KeyError because the JSON payload it parses to determine the units doesn't contain the keys it's looking for.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
weather:
  - platform: darksky
    api_key: !secret darksky_api
    mode: hourly
    name: "Hourly Forecast"

Traceback (if applicable):
2019-01-30 00:19:00 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py",
line 239, in async_update_ha_state attr = self.state_attributes or {}
File "/usr/lib/python3.6/site-packages/homeassistant/components/weather/__init__.py",
line 125, in state_attributes self.hass, self.temperature, self.temperature_unit,
File "/usr/lib/python3.6/site-packages/homeassistant/components/weather/darksky.py",
line 114, in temperature_unit return TEMP_FAHRENHEIT if 'us' in self._dark_sky.units \
File "/usr/lib/python3.6/site-packages/homeassistant/components/weather/darksky.py",
line 241, in units return self.data.json.get('flags').get('units')
AttributeError: 'NoneType' object has no attribute 'json'

Additional information:
Issue is here: https://github.com/home-assistant/home-assistant/blob/master/homeassistant/components/weather/darksky.py#L241
The solution would be to return some default value or derive the units from some other means, and I'm open to suggestions on how to resolve this.

Duplicate of #16898, but seems like your fix (#22101) did not solve the issue, as the error now is raised in a different location.


Made the Navigation page where in train navigation system, users would search for routes between two stations, and the system would show available trains, timings

✨ Feature Request
Description of the Feature
For a train navigation system, users would search for routes between two stations, and the system would show available trains, timings, and possibly other details like travel duration or stops. We can allow users to input two stations (departure and destination) and find trains available between those stations, showing relevant details like train names and timings.

[x] Yes
[ ] No

@dhairyagothi  assign me this so i will make a pr and i made a whole new component and i have seen there is no issue here


[HUDI-6023] HotFix in HoodieDynamicBoundedBloomFilter with refactor arguments in HoodieDynamicBoundedBloomFilter

Change Logs
HotFix in HoodieDynamicBoundedBloomFilter with refactor arguments in HoodieDynamicBoundedBloomFilter
Impact
not any impact to other moudles
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

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

Contributor's checklist

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

cc @danny0405

@hudi-bot run azure

@hudi-bot run azure

@danny0405 hi，teacher，two CI process is finised successfully


Ally-compliant color palette & functions

This PR, which effects every component that used the foreground() function, addresses #7387. I've adjusted the $foundation-palette to meet AA contrast requirements. The foreground() function has been replaced with a new pick-best-color() function that uses luminosity instead of lightness (which fails as #7387 explains).

While replacing foreground() with a function that uses luminosity, I noticed that Tabs is using foreground() for the content font color. There's really no reason for this, as the content background color is explicitly set. Now $tab-content-color is just simply set to $body-font-color.
I also noticed that Tabs' mixins didn't allow for passing any vars when creating your own tabs. Fixed this too.
Finally, I added settings for tab item font colors. You could previously set the tab items' background, but not their color.

Just like Tabs, it's the same case for Accordion & Pagination (foreground function sets the text color but the background color is explicitly set, and mixins don't pass vars). Fixing those too…

:+1:
Wouldn't color-contrast() / color-*() / pick-contrast-color() (but I prefer a function with a namespace) be better than pick-best-color() ?

I can change that to whatever everyone agrees is most semantic. That's just what the function is called in the gist from which I ported the luminosity functions. I've updated the function (and its description which was old/wrong) based on your feedback. Thanks, @ncoden!

Travis failure appears to be real - @andycochran can you take a look?

I don't know why sass-true crash now. But we can try with node v4.0.

v4.2.2 throws the same error:
Error: Undefined operation: "0.2126 times pow(0.99628, 2.4)".
    at Object.module.exports.renderSync (/Users/kball/git/foundation-sites/node_modules/n
ode-sass/lib/index.js:440:16)
    at Object.module.exports.runSass (/Users/kball/git/foundation-sites/node_modules/sass
-true/lib/main.js:34:18)
    at Object.<anonymous> (/Users/kball/git/foundation-sites/test/sass/test_sass.js:14:10
)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)

Found the issue. The scss tests import files individually... this PR introduces a dependency for color on math.  You can fix the failure by adding an @import 'math' into _color.scss

I can fix the above issue as a part of the merge if you like.  Other than that, is this ready to go @andycochran @ncoden?

@kball fixed. I think this is good to go so long as Zurb is cool with the new ally-compliant color palette. It's not as vibrant. I also wouldn't mind a "LGTM" from @ncoden or @brettsmason.

Hmm… looks like Travis is still upset.

Bah, kicking travis, looks like that spurious phantom download error.
@zurbrandon @tdhartwick @gakimball any of you have thoughts on this new default palette?

@ncoden Thanks for the feedback. I'll work on this tomorrow.

FYI, here's the diff in the colors:

Can't we keep background colors for a white text ?

@ncoden In order to keep white text for the Success and Warning buttons, the colors have to darken quite a lot.

 They meet AA requirements with the alt text color.

@andycochran I understand. But the different text colors disturb me. And I don't find the disabled text very visible.
Maybe we should change the hue, saturation and luminosity to have beautiful and ally-compliant colors.

@ncoden I'd love it if we could come up with that palette. But AA contrast requirements quite limiting. I think we can only get two out of these three: 1) beautiful 2) ally-compliant 3) white text. Please feel free to propose new colors.
I imagine most designers who don't care about AA requirements will simply set [component]-color and [component]-color-alt to the same value—e.g. white. :cry:
Maybe the alt text color is visually awkward because all the buttons are shown in a row here? In practice, buttons won't often be arranged this way.

@andersonaguiar
I'll search for better colors that meet these three critera. Otherwise, I would prefer beautiful and white text. I care about a11y, but not if it break the design for everyone.
Also, In practice, I often see a primary button next to a warning button. :/

:frowning_face: Caring more about aesthetics than a11y is directly opposed to the spirit of #7387.
@kball / @rafibomb, can Zurb and its designers can weigh in on this?

I checked with WebAIM, and didn't find a a11y-compliant (AA) color for a white text that is not ugly. :disappointed:  Also, disabled button have a .25 opacity, so the background color is not relevant at all for a11y tests.
But could we, instead of changing the default colors, provide a set of tools to help websites to provide an alternative A11y High Contrast color palette dynamicly (like DuckDuckGo).
Also, Firefox allow the user to overriding the page colors (but not Chrome).

Don't worry about contrast for .disabled.

But even tough the guidelines do not require a contrast ratio for disabled UI components, I think the current style for the disabled buttons (opacity: 0.25) is a bit too light/has too low contrast ratio. Maybe the number could be tweaked at least a little bit.
– @Owlbertz's comment in #7387

Again, I think this comes down to a judgement Zurb should make. Should Foundation Sites actually be "fully-accessible" as advertised, and must that include meeting AA contrast requirements out-of-the-box?

We are focusing so much on accessibility with the framework that imo we should make it be compliant out of the box. Of course this is a thing that the ZURBians have to decide, but as we are promoting to be "fully-accessible" as @andycochran said this should be the goal. Maybe we have to go even further and add some contrast checking to the SASS and/or the "custom download" page.
The biggest problem with a11y will always be that people are not aware of it or just don't care and thus we should give them as much help as we can to create compliant websites so they'll actually do.

The updated compliant palette @andycochran suggested is a super solid compromise. @shannon-zurb and I tinkered with the palette this morning and arrived at a similar conclusion - white text on green and yellows is hard to make look beautiful and accessible.
Question came up in the office here - should we make the compliant palette a variable that can be disabled (or enabled)? We fear that defaulting the framework's color palette to be compliant maybe regressive. Sites may have intentionally used the current out-of-the-box colors because it aligns with their brand. @zurbrandon @tdhartwick

@MandiSaeteun I don't think an extra variable just to turn on a11y colors is necessary—especially if it's on by default. Just as easily as turning it off, you could set your alt-colors to white. If this was a patch, I might agree that we shouldn't break folks' button colors. But it's a minor version with other changes that require reviewing your _settings.scss. Isn't advocating for AA compliance is more important than not bothering people to review the new version's settings?

Looks like there are some new conflicts. I'll get these fixed…
@kball / @MandiSaeteun, any further thoughts from Zurb on out-of-the-box compliance?

I think the callout have similar problem, in the setting they are a $callout-font-color-alt but never used and it sould be great if the background is dark the alt color is used.

@andycochran Our consensus has been that out of the box compliance is very important, and worth sacrificing a little bit of backwards compatibility.  Lets write a migration note that addresses this and lets people know how they can revert to the previous palette.  Other than this, is this ready to merge?

@kball AFAIK, it's ready to merge. Didn't wanna add that label to my own PR tho.

Merged!  @andycochran can you write a quick migration note (comment in this PR would be fine) highlighting what the change is and how someone would get back to the previous palette if they wanted to?

Migration notes
New functions

The foreground() function has been replaced with a new color-pick-contrast() function that uses luminosity instead of lightness.

The color-pick-contrast() function requires new _math.scss utilities for 1) finding the greatest common divisor of two integers and 2) handling decimal exponents by trying to convert them into a fraction and then use a nth-root-algorithm for parts of the calculation.

Revised settings

The $foundation-palette variables have been adjusted to meet WCAG 2.0 level AA contrast requirements. For backwards compatibility (ignoring AA requirements), revert primary to #2199e8, secondary to #777, and alert to #ec5840.

All instances of the foreground() function have removed from _settings.scss in favor of setting explicit colors and alternate colors.

The $tab-content-color and $pagination-item-color-current variables are now set explicitly. There's no need for a function to determine these color, as their associated background colors are also set explicitly. Previously, the foreground() function for Pagination only allowed for black or white text.

New settings variables

The Badges and Labels components now have alternate colors: $badge-color-alt and  $label-color-alt. These are used the same way as $button-color-alt. The $badge-color and $label-color now default to white (like $button-color). Previously, the badge and label colors defaulted to a function which made assumptions about the lightness of the background colors. Buttons, Badges, and Labels components now all work the same way. The default can be any foreground/background color combination, and for each background color defined in $foundation-palette, the foreground is automatically set to the color or alternate color (whichever has more contrast). For backwards compatibility (ignoring AA requirements so all button colors have white text), set the alt colors to white.

The Tabs component now allows you to set the color of tab titles with $tab-color and $tab-active-color. Previously, tab titles were hardcoded to the primary color, which was not visible on some tab background colors.

Mixins

Accordion, Pagination, Tabs now allow for passing vars when creating your own components.

@andycochran I think it would be valuable to add a note to the docs for buttons, badges, and labels that explains why they have mixed text colors out of the box, and how to change it to all white (with a warning that it will reduce your contrast below AA contrast requirements)

@kball Will do…


Compile dependency on a projects Magma vault when using the project as a dependency

When using a library that integrates moduledocs via use Magma from the Magma vault, there is currently a dependency on the library's Magma vault that is not present by default.

Although the project using the dependency will compile without problems, it will compile the modules without the moduledocs. So, if you decide to include your moduledocs with use Magma, be aware that if you're writing a library and your users should be able to use these docs on their machines, e.g. with the h helper in IEx you'll have to include the Magma documents with the final moduledocs in your package like this:
defp package do
  [
    # ...
    files:  ~w[lib priv mix.exs docs.magma/artefacts/final/modules/**/*.md]
  ]
end

The docs were updated to include a respective note.


Random Choice when doing prediction

I am not sure why you you did the random prediction this way action = np.random.choice(self.action_space, p=prediction) also you are picking the random outcome as the chosen action during testing and training. I can understand why during training but why during testing as well  ?

You right, I shouldn't do this while testing

I don't think it's wrong if you look at the way that the choice method works. It selects one of the actions based on the probability set by the prediction. The reasoning for it in training makes sense but for testing I can't be sure. It does seem like it might randomly choose something that will cause it to lose.

I realised this also and tried different things.
Random choice works well with training but testing becomes better with a number.
Best result I could achieve was to make the action when the probability/prediction is more than 67%.

how can we conect this bot to demo exchange?


Add websocket implementation

This adds a wrapper around the WebSocket API of SurrealDB as it is more feature-ful than the REST API, providing people with the ability to use either.

unfortunately the commit history is quite messy for this, it requires https://github.com/surrealdb/surrealdb.py/pull/5 for merging but includes the history from that PR too.
if anyone would like to help out with typing the request & responses for this that would be great, since there is no documentation for them nor any typing on the other language's libraries; i would not have to keep response & return types as Any :P

PR good to go! some typing may need to be improved further down the line when we have better docs, but based on everything explained on discord it can't really get any better currently.
authentication, creating records & reading records has been tested; if anyone wants to test the rest before-hand then feel free!

see https://github.com/surrealdb/surrealdb.py/pull/6#discussion_r973738089

added #7 to http client, resolved merge conflicts. good for merge!


Update DG: add use case for vliste

suggest to identify all event-volunteer use cases by UCEV thoughts?

suggest to identify all event-volunteer use cases by UCEV thoughts?

hmm fair imo

i like how all of us decided to do use cases like rn cos i didn't realise u and max also did it


Minecraft is not responding [Multiconnect].

When Tooltip is being rendered as below:
Th-
-is
-a-
to-
-ol
-t-
-ip
it causes minecraft to not respond. Tooltip should be rendered on the left side of the mouse pointer, but it didn't.

Ah, i forgot to mention that you can reproduce it by hovering on version button in direct connection screen with multiconnect

Are you using the latest release of tooltip fix? I'll investigate tomorrow

I redownloaded whole game and now it works as it should.


Flappybird

PR Description 📜
This is a game made using html , CSS  and JavaScript . It can responsive graphics and background sounds .
Fixes #1768

Mark the task you have completed ✅

[ x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x ] I have performed a self-review of my own code or work.
[x ] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x ] I have added screenshot for website preview in assets/images
[x ] I have added entries for my game in main README.md
[x ] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Teddy1404 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

I updated the readme file and the image is already in images folder inside assets.

we already have this game on GameZone 👀 !!!

Thank you  @Teddy1404 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Made the NavBar hover effect consistent for all the 3 pages , Fixes : #175

Updated contri.css , about.html and contributers.html files.

Hello @Shreshth-Srivastava  👋,
To ensure our development process runs smoothly, we kindly request that you follow this workflow:
Issue Assignment 📝: Before you start working on any issues, please make sure that the issue is assigned to you. If it's a new issue, create one if it doesn't already exist.
Avoid Direct PRs 🚫: Refrain from creating direct pull requests (PRs) for issues that are already assigned to someone else. This helps prevent duplicated efforts and keeps our work organized.
Collaboration 🤝: If you find that an issue is already assigned to someone and you're interested in working on it, feel free to comment on the issue. If the first assigned person isn't able to complete the task or doesn't create a PR, we can reassign the issue to ensure it's addressed properly.
Your cooperation is greatly appreciated, and it helps us maintain an efficient and collaborative development process. 🙌
This issue #175 is assigned to @092vk ...


Can you play a video on game over in LUA?

Describe your problem here.
Is there a script or event or anything that when you die, it plays a video like in too fest 2.5?
You know, but in LUA... cuz my computer wont let me download source for some reason?

Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

function onGameOver()
playVideo('video');
return Function_Stop;
end
return Function_Continue;
you can try this but idk if it works properly or no

I’m sorry you’ve been caught up in the “nimu” mess

I’m sorry you’ve been caught up in the “nimu” mess

I took down one of their accounts

I’m sorry you’ve been caught up in the “nimu” mess

Nimu mess?

I’m sorry you’ve been caught up in the “nimu” mess

Nimu mess?

It's a long story


print zip file hash during start

Problem
for app store publishing, it's a slight hassle to find the package zip hash from inside of the vfs of the node you're trying to serve it from.
Solution
print it upon start (perhaps write it into metadata.json automatically too? (this seems like too much to me, but perhaps gate behind a flag)
Docs Update
Corresponding docs PR
Notes
kit s
simtester:template.os
package zip hash: be8a31d6fc1fcea9395c10ecf3486fdde3c86ee61a8ab7f15211717d555fb474
Successfully installed package simtester:template.os on node at http://localhost:8080

A couple changes. Aside from that, could you give me some more context for the problem we're trying to solve here? Is this for app store publishing? If so, why would we not write the hash to the metadata.json? That seems like a strictly better devex to me, especially considering we should be able to grab the current version number from Cargo.toml and then either overwrite or add to the metadata.json code_hashes field.

Yes for app_store publishing ergonomics. Grabbing the current version number from Cargo.toml assumes that such a file exists in the package root (it might not) + that its version number is kept updated by the developer. I think it makes more sense as a light print for correctness/a helper for developers, rather than explicitly modifying files within the same package

@bitful-pannul please MAKE SURE that the printed hash is CORRECT, meaning, usable for a successful download!!!!

@bitful-pannul please MAKE SURE that the printed hash is CORRECT, meaning, usable for a successful download!!!!

check!


javax.net.ssl.SSLProtocolException: Read error: ssl=0x7efd216488: Failure in SSL library, usually a protocol error     error:10000416:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN (external/boringssl/src/ssl/tls_record.cc:587 0x7f0bb4ea48:0x00000001)

server is win server 2008R2 and .net core 3.1, app request with a .pfx certificate.
onFailure：
javax.net.ssl.SSLProtocolException: Read error: ssl=0x7efd216488: Failure in SSL library, usually a protocol error     error:10000416:SSL routines:OPENSSL_internal:SSLV3_ALERT_CERTIFICATE_UNKNOWN (external/boringssl/src/ssl/tls_record.cc:587 0x7f0bb4ea48:0x00000001)

This isn't a reproducible bug report, please consider using a site like stackoverflow with a concise correct example.  Also without access to your server or certificates there is not much we can help with.
This just means that we can't establish a trusted connection between client and server.
https://github.com/grpc/grpc-java/issues/6374


AWS ingress

Currently people just stick a Service of Type=LB in front of the nginx ingress on AWS. Apparently, this causes some issues, and an ALB works better (https://github.com/sky-uk/feed/issues/111). Maybe we should actually write an AWS ingress controller that spins up an ALB so people can tier it over the nginx ingress key-ing off ingress.class=aws/nginx ?
ref https://github.com/kubernetes/contrib/issues/346
@jsravn @justinsb

ALB while very scalable is also still quite limited.
Plain old TCP ELB with proxyprotocol (full handoff to nginx) seems to work fine for me in AWS.

I'm sure we'll end up supporting ALB eventually.  But ... what are the issues that ALB solves over ELB + ingress?

ELBs will return 504s occasionally when nginx does a reload. ALBs don't have this problem.
Number of 504s correlates to the load on the ELB - it isn't many (probably less than 1% even under load), but it happens. Even with TCP ELB - you'll just get a reset connection instead.

ELBs will return 504s occasionally when nginx does a reload. ALBs don't have this problem.

When running in tcp proxyprotocol mode this doesn't happen. A more generic problem with using nginx specifically is it resets the loadbalancing counters on config reloads, causing more load on the "first" pod in the backend for a service. That means you can run into cascading errors on busy sites as the "first" pod dies due to the load, causing a new config loads, etc.

Do we know why nginx reload is being surfaced as a 504 as well?  I was under the impression that nginx didn't drop connections during a HUP.  Is it a matter of decreasing the ELB timeout so that it is less than some nginx timeout?

@jsravn @pieterlange could you provide an example/guide that reproduces the described error?

ALBs now have host-based routing https://aws.amazon.com/blogs/aws/new-host-based-routing-support-for-aws-application-load-balancers/
so they seem a yet better fit for Ingress; not sure whether they support multi-cert-TLS termination (or any)

ALBs also (same blog post) now support 75 routes per balancer, rather than just 10

Closing. Current catalog contains a link to an ALB ingress controller.


Pin to specific version of libreselery

Otherwise updates could break builds.
We should still employ semantic versioning, so you stil get updates of minor versions, but not automatically pull major version updates.

I will move that issue to the main project to add it to the milestone.


Fail fast if cannot initialize logSink

What this PR does / why we need it:

When trying to use Kafka LogSink but failed to initialize NewKafkaSink, the getLogSink function returns nil and the program continue running. This can lead to panic because the program trying to use nil value when trying to Send the payload log:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xf2359d]

goroutine 31 [running]:
github.com/caraml-dev/merlin/pkg/inference-logger/logger.(*Worker).Send(...)
	/src/log-collector/pkg/inference-logger/logger/worker.go:106
github.com/caraml-dev/merlin/pkg/inference-logger/logger.(*Worker).Start.func1()
	/src/log-collector/pkg/inference-logger/logger/worker.go:79 +0x5dd
created by github.com/caraml-dev/merlin/pkg/inference-logger/logger.(*Worker).Start
	/src/log-collector/pkg/inference-logger/logger/worker.go:40 +0x56

This PR modifies getLogSink to also return error and fail faster if it failed to initialize KafkaSink.
Which issue(s) this PR fixes:

Fixes inference-logger raise panic.
Does this PR introduce a user-facing change?:

NONE

Checklist

[ ] Added unit test, integration, and/or e2e tests
[x] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

Btw, how can we fail fast for NewRelic logger?

Btw, how can we fail fast for NewRelic logger?

NewRelic library does not have a built-in Ping API like Kafka, so instead, I think we can build and send our own "ping" log to NewRelic after NewRelicSink initialization.