Enhance Footer Social Icons with Hover Effects

I would like to propose an enhancement for the social icons in the footer. The icons should change color and increase slightly in size when hovered over to improve user experience.
Details:
Facebook Icon: Change color to blue on hover.
Instagram Icon: Change color to pink on hover.
Size Increase: Slightly increase the size of the icons on hover.
Expected Behavior:
When a user hovers over the social icons:
The Facebook icon changes to blue.
The Instagram icon changes to pink.
All icons increase in size slightly.
Additional Context:
This enhancement will make the footer more interactive and visually appealing, providing a better user experience.
Can u assign this issue to me under GSSOC -2024 extd .

@Shekhar-Raj please give preview video of your idea.

@Anjaliavv51 I'd be glad to contribute...here is the clip where I've enhanced the footer icons...
can you assign this issue to me
https://github.com/user-attachments/assets/947cd4d1-d407-484c-918d-fa99002c02fe

@Shekhar-Raj please go ahead.

@Shekhar-Raj please go ahead.

Thanks will be back!

Could you assign this issue to me

no it already assigned.


Subctl v0.6.0-rc03: Service discovery on supercluster.local: Name does not resolve

This issue is reoccurring since last Friday:
https://qe-jenkins-csb-skynet.cloud.paas.psi.redhat.com/job/Submariner-OSP-AWS/789/Test-Report/
https://qe-jenkins-csb-skynet.cloud.paas.psi.redhat.com/job/Submariner-OSP-AWS/790/Test-Report/
$ oc describe serviceexport nginx-cl-b

Name:         nginx-cl-b
Namespace:    test-submariner
Labels:       <none>
Annotations:  <none>
API Version:  lighthouse.submariner.io/v2alpha1
Kind:         ServiceExport
Metadata:
  Creation Timestamp:  2020-08-23T05:25:20Z
  Generation:          3
  Resource Version:    7799204
  Self Link:           /apis/lighthouse.submariner.io/v2alpha1/namespaces/test-submariner/serviceexports/nginx-cl-b
  UID:                 fcbda95e-90d3-48d2-b0d4-d972624f5d32
Status:
  Conditions:
    Last Transition Time:  2020-08-23T05:27:28Z
    Message:               Awaiting sync of the ServiceImport to the broker
    Reason:                AwaitingSync
    Status:                True
    Type:                  Initialized
    Last Transition Time:  2020-08-23T05:27:28Z
    Message:               Service was successfully synced to the broker
    Reason:
    Status:                True
    Type:                  Exported
Events:                    <none>

$ oc exec netshoot-cl-a-new -n test-submariner -- ping -c 1 nginx-cl-b.test-submariner-new.svc.supercluster.local
ping: nginx-cl-b.test-submariner-new.svc.supercluster.local: Name does not resolve

Environment:
Subctl v0.6.0-rc0-3
Cluster A (AWS):
Client Version: 4.5.6
Server Version: 4.5.6
Kubernetes Version: v1.18.3+002a51f
Cluster B (OSP):
Client Version: 4.5.6
Server Version: 4.4.3
Kubernetes Version: v1.17.1

This has been fixed by: https://github.com/submariner-io/submariner-operator/pull/645
On My tests I see that with SubCtl v0.6.0-rc0-5-g555be51 - Supercluster is still supported:
PING nginx-cl-b.test-submariner-new.svc.supercluster.local (<IP_ADDRESS>) 56(84) bytes of data


'Text Position' setting

Option for where the text should be displayed relative to the icon. Left and right are obvious choices, but it would also be nice to add options for displaying the text in the corner of the icon with a cutout, similar to how the data indicator should be displayed next to the network icon.

I have tried implementing this and it will clutter the icon settings considerably, so this should wait for #115.


fix: checkbox disables and clears input when checked

Page state does not go back to "" when the checkbox is clicked

Page state does not go back to "" when the checkbox is clicked - is that intended?


fix(updates): set NODE_ENV environment variable so that npm does not filter

When running npm ls, if npm detects a NODE_ENV environment variable it will filter dependent on
that, atom will set this to production which means that npm ls will not return the global packages,
so explicitly set it to undefined so we can correctly get those packages.
Maybe I'll remember this next time

Messages

:book:

:white_check_mark: All tests are passing
Nice one! All 42 tests are passing.

  Generated by :no_entry_sign: dangerJS against 801f403e7795bb460d8ffb5c839e34115205862b


Save playlist created a playlist based on another song

I got a playlist recommended on my song, but when I clicked to save it, I got a whole another playlist based on another song (which was very good no doubt).
Pretty sure this is unintended behavior.
Great app though.

@Parth-Vader Did you make sure to click on "Generate Recommendations" before saving the playlist?

This has become a confirmed bug. Moving all future comments regarding this issue to issue #6
Thank you for reporting this.


⚠ SceneTime has degraded performance

In 0f5033f, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1787 ms

Resolved: SceneTime performance has improved in 2db88b7 after 6 minutes.


Brute Forcing

How to avoid brute forcing? It times too much time.

Amass
flag provided but not defined: -d


Graphql image

This PR should add support for images in Frontmatter.

I'll merge this in as it is now. We can add arguments etc. later. Thanks for the work you've put into this :)


@perseidesjs/medusa-otp unable to add in npm

Error starting server
Error: Unable to find plugin "@perseidesjs/medusa-otp". Perhaps you need to install its package?
i have tried installing by npm  i @perseidesjs/medusa-otp am getting below error

rak@Prakashs-MacBook-Air commerce % npm i @perseidesjs/medusa-otp
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/@hookform/error-message/node_modules/react-hook-form
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/@hookform/error-message
npm WARN<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN   node_modules/@medusajs/admin-ui
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@medusajs/medusa
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/medusa-file-spaces
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/medusa-file-s3
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   17 more (medusa-payment-stripe, medusa-test-utils, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@rsc-labs/medusa-affiliate-discount
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@medusajs/medusa
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@rsc-labs/medusa-affiliate-discount
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/prak/.npm/_logs/2024-08-21T11_24_34_531Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /Users/prak/.npm/_logs/2024-08-21T11_24_34_531Z-debug-0.log

Hi @prakashrandy18 !
Sorry for the late answer, it's because it should be @perseidesjs/medusa-plugin-otp and not @perseidesjs/medusa-otp 🙌
I've updated the typo on the docs just right now

Yes, You're right..Thank you @adevinwild for the response.


Added musl linux build targets

Hopefully resolves #723 - adds two targets to the release matrix of Actions Workflow.
I also changed conditional for adding targets via rustup target add to happen for every target - mainly for consistency, but also because fromJson clause becomes more and more lengthy. I'm also open for discussion whether this step should actually happen at all, I haven't seen it in other Rust repos.
Cheers!

Hi, thanks for the PR! I got this error when testing it:
  running: "musl-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "/home/runner/work/yazi-test-musl/yazi-test-musl/target/x86_64-unknown-linux-musl/release/build/onig_sys-7f6e2cee5be0aba3/out" "-I" "oniguruma/src" "-DHAVE_UNISTD_H=1" "-DHAVE_SYS_TYPES_H=1" "-DHAVE_SYS_TIME_H=1" "-o" "/home/runner/work/yazi-test-musl/yazi-test-musl/target/x86_64-unknown-linux-musl/release/build/onig_sys-7f6e2cee5be0aba3/out/oniguruma/src/regexec.o" "-c" "oniguruma/src/regexec.c"

  --- stderr

  error occurred: Failed to find tool. Is `musl-gcc` installed?

warning: build failed, waiting for other jobs to finish...
Error: Process completed with exit code 101.

And the test repo here https://github.com/yazi-rs/yazi-test-musl/actions/runs/8119836215/job/22196249096

Still can't make aarch64 musl linux build as we're dealing with some linker errors:
  = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname)
error: could not compile `yazi-fm` (bin "yazi") due to 1 previous error

I've isolated just musl targets on a separate branch to test things out (shoulda done it initially I guess, sorry! :D): https://github.com/uznog/yazi/actions/runs/8123545617/job/22204066982
I installed musl-tool, which makes x86_64 build work, but adding musl-dev doesn't make a difference. Tinkered with CC / RUSTFLAGS env variables with no luck as well and I'm kinda out of ideas, but I'm no Rust pro so I might be overthinking, any tips are welcome. GNU gcc for aarch64 should be able to compile it as of #https://github.com/rust-lang/stacker/issues/80#issuecomment-1547991131

No worries! I will play around with the other options and see if I can get this fixed.


How to round a floating point division up?

Does Crystal have some kind of ceiling function?
puts (10_f32 / 4).ceiling    # print 3

Assuming there isn't such a function, I will try to implement it and issue a pull request. I've never done a pull request before, so it'll be useful experience.

Yes, it's called ceil:
puts (10_f32 / 4).ceil    # print 3

Oh, fair enough ;)
I guess the github practice can wait then.

Maybe http://stackoverflow.com/questions/tagged/crystal-lang would be a better place for questions about Crystal.

Shouldn't ceil return an int?

Yes, please ask in stack overflow as these aren't really issues or bugs.
It returns a float because if the float is very big there's no way to represent it with an int. If you are sure it fits in an int, call to_i afterwards.


v19.1.5 improved test environment

[Current coverage][cc-pull] is 100%

Merging [#489][cc-pull] into [master][cc-base-branch] will not change coverage

File ...RequestValidator.php (not in diff) was modified. more

Misses 0
Partials 0
Hits +18

@@           master   #489   diff @@
====================================
  Files          27     27
  Lines         420    438    +18
  Methods       105    114     +9
  Messages        0      0
  Branches        0      0
====================================
+ Hits          420    438    +18
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last updated by [f934128...7655f5b][cc-compare]
[cc-base-branch]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/compare/f9341286dff90f36c526e8f338d502d96dd5ba9b...7655f5b54effc13d2a1db21e5bbd28b104de2722
[cc-pull]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/pull/489?src=pr


Video API in WeChatBrowser(x5 engine) can't render？

Version

Phaser Version: 3.23.0 - 3.24.1

Operating system:iOS 12-14

Browser:WeChat Browser ( x5 engine )

Description

When I use Video API in Wechat Browser, the console remind me "TypeError: null is not an object (evaluating 'this.frame.realWidth')"
When I check 'Phaser.scene.cache.video' ,it shows that Map Struct's size is 0.
On the contrary, it’s available in PC Chrome and Mobile Phone Browser, the video rendered successfully and the Map Struct's size is 1.
See additional information for details.
Example Test Code

load : this.load.video('key','url',true,false)
scene: this.add.video(0,0,'key');
Additional Information

PC console:

ios console:

Are you sure this is a video format that WeChat is capable of playing? have you tested the video outside of Phaser? (like in a simple HTML video component)

Are you sure this is a video format that WeChat is capable of playing? have you tested the video outside of Phaser? (like in a simple HTML video component)

i'm familiar with this platform, it's not a fault of Phaser, because Phaser loads video with <video> tag in VideoFile loader type, but this tag is just not available on this platform. to create a video on this platform, there is its private API: wx.createVideo(...);
@luvsta if you wanna do this, you have to customize your own loader filetypes (https://github.com/photonstorm/phaser/blob/master/src/loader/filetypes/VideoFile.js FYI), and register it into the file manager:
FileTypesManager.register('wxVideo', ...... {  this.addFile(new YourOwnFileType(...));  });

Useful info, thanks!

@jcyuan thx bro,I realized that the WeChat browser was blocking the load event，and i fixed that using 'wx-js-sdk' ,wrapping code behavior as user behavior.

@photonstorm Yes, I found out later that it was a browser limitation


Opening two projects in two windows results in infinite loop of reloading

VSCode Version: 1.29.0
OS Version: macOS 10.14

Steps to Reproduce:

Open a project in one window with File -> New Window, File -> Open Recent
Open a project in another window with the same steps.

Does this issue occur when all extensions are disabled?: NO
One of the projects was an Ionic project and the bug seems to stop when I disable this extension.
Video of the bug occurring here

That's strange. It would be great if you can also file this on that extension and maybe they can help us understand why they might be causing the window to reload.


Personal access tokens

Closes #1462

@whisperity First we try to authenticate the user by personal access token:
https://github.com/csordasmarton/codechecker/blob/1ef2259133f9b34c03b2b5cb6cb0fd58bada5930/libcodechecker/server/session_manager.py#L421

@csordasmarton That I understand. I can't figure out in the clientside code where it is handled that the auth token is sent.

@whisperity The user can use these generated personal tokens instead of passwords. For example in the .codechecker.passwords.json file the user can use this token instead of the password:
{
  "client_autologin" : true,
  "credentials": {
    "*" : "username:token"
  }
}

Okay, I get it now. But there isn't any automation, i.e. creating a new token does not add it to the file by default. There also isn't an option at login (or at any cmd command) to specify the token to use.
I don't believe that there should be automation or an extra argument, but this should be at least documented, your previous reply with some flavour text.


grouped reduce in area and line marks

closes #724 (and #503)
todo:

[ ] avoid the multiplication of the reduced value(s) to the whole channel
[ ] reuse the group reducers if possible?

supersedes #508

This is still materializing a mapped channel even though we only need a single value. And as you noted it doesn’t use the existing reducers. I’ll try to take a crack at this soon, but I want something that does both of these things before merging.

yes a bit more work is needed. I wanted to rebase and clean up the previous PR so we could make progress on this.
To sum up the current status: this is suboptimal because it populates a channel with n copies of the reduced value. But I've been struggling with the fact that we can't reduce to a single value either: we need a channel, because we have to carry an element for each line or area. The difficulty is that the reduction must to happen in a grouped transform (z + facet, like map does), in a manner that is compatible with Plot.window, before we apply scales, and before we group.

Should we close this, since we landed #761?

Yes. I still think there is value in the Plot.reduce helper described in https://github.com/observablehq/plot/issues/724#issuecomment-1024937329.


HIVE-25321: advance write id during AlterTableDropPartition

Why are the changes needed?
Advance Write ID during AlterTableDropPartition DDL
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit tests

Looks good to me.

It's failing during "Archiving" stage with below error, which seems to be intermittent. Hopefully I will get a green run in the next one.
[2021-07-15T06:00:07.621Z] java.net.ProtocolException: Expected HTTP 101 response but was '500 Internal Server Error'
[2021-07-15T06:00:07.621Z] 	at okhttp3.internal.ws.RealWebSocket.checkResponse(RealWebSocket.java:229)
[2021-07-15T06:00:07.621Z] 	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:196)
[2021-07-15T06:00:07.621Z] 	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203)
[2021-07-15T06:00:07.621Z] 	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
[2021-07-15T06:00:07.621Z] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[2021-07-15T06:00:07.621Z] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[2021-07-15T06:00:07.621Z] 	at java.lang.Thread.run(Thread.java:748)
io.fabric8.kubernetes.client.KubernetesClientException: error dialing backend: EOF

@nrg4878 One unrelated test is failing now http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-2465/12/tests . Please commit this change, whenever you get time.

@nrg4878 Got a green build -> http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-2465/13/pipeline/ .

fix has been committed to master. Please close the PR. Thanks


Add native support for camel-quarkus-management

Describe the feature here
Since there is now experimental support for JMX in GraalVM, we could investigate adding some initial support for it in the camel-quarkus-management extension.
I did some very brief hacking and got to view the Camel MBeans:

@jamesnetherton Wow, so could we run JMX with native build?

@jamesnetherton Wow, so could we run JMX with native build?

Yes, this provides native JMX support for Camel. Jolokia in native mode for HawtIO will probably bring its own set of problems that would need investigating. But we now have a basic starting point at least.

@jamesnetherton Awesome !


Revert "fix(cpu): Replace %percentage-cores% normally"

Reverts jaagr/polybar#1422

Codecov Report

Merging #1431 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1431      +/-   ##
=========================================
- Coverage    5.84%   5.83%   -0.02%
=========================================
  Files         161     161
  Lines        8919    8935      +16
=========================================
  Hits          521     521
- Misses       8398    8414      +16

Flag
Coverage Δ

#unittests
5.83% <0%> (-0.02%)
:arrow_down:

Impacted Files
Coverage Δ

src/modules/cpu.cpp
1.08% <0%> (-0.08%)
:arrow_down:

include/components/config.hpp
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Support folders in path for ZipFileDataFormat#marshal

The ZipFileDataFormat#marshal now uses the full path given in the FILE_NAME header as the name for the ZipEntry. This way it will create the specified folders in the generated zip file.
The out FILE_NAME header however still uses the pathless version of the in FILE_NAME header.

Folders are not added as seperate entries. That would be strange i suppose.

And would it not be s major change for the current users of component?

@onders86 That is a valid point, even if we keep the removal of path elements for the FILE_NAME header intact, and use the FILE_PATH header for path assignment it could cause changes for current users.

See my latest comment upwards too. It is a bit of new feature cuz it breaks backwards compatibilty. Discussion needed i guess

I guess we could always add an option like preservePathElements to the data format and default it to false, in order to maintain backwards compatibility.

Sounds fair. Could you also check for the camel-tar? Itis almost the same

Could you please squash your commits?

@onders86 I'll squash my commits and check about your windows comment later today.

If there is a new option to turn this on|off it needs to be added to camel-core as well when you use dataformats.

@Vreijsen you need to add the option in camel-core to turn this on | off. And its double work as we need this for zipfile and tarfile data formats.

@davsclaus I'm aware, unfortunately, i was quite busy the last couple of days in which I couldn't work on this PR. I will continue this weekend!

@davsclaus I added the options in camel-core to turn this on | off, both for ZipFileDataFormat and TarFileDataFormat. Regarding @onders86 's comment about using / as path separator in the ZipEntry and TarEntry I believe this is supported by Windows as well:

4.4.17 file name: (Variable)
   <IP_ADDRESS> The name of the file, with optional relative path.
   The path stored MUST not contain a drive or
   device letter, or a leading slash.  All slashes
   MUST be forward slashes '/' as opposed to
   backwards slashes '\' for compatibility with Amiga
   and UNIX file systems etc.  If input came from standard
   input, there is no file name field.

Source: zip specification

@Vreijsen thanks, can you fix the checkstyle errors
mvn compile -P sourcecheck

In camel-core and those other components you have changed


Feature Request: Add PostgreSQL Primsa Support for NestJS

Description: I recommend exploring the integration of Prisma ORM into StartEase, offering an alternative for developers familiar with it. This could enhance our project's flexibility and efficiency.
And I'd like to work on the feature.

okay great . will assign this to you


gherkin/java: Ignore unknown fields

Protobut is both backwards and forwards compatible. So it doesn't make sense to strictly
parse all fields
Types of changes

[X] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

[X] The change has been ported to Java.
[x] The change has been ported to Ruby.
[x] The change has been ported to JavaScript.
[x] The change has been ported to Go.
[ ] The change has been ported to .NET.
[ ] I've added tests for my code.
[ ] I have updated the CHANGELOG accordingly.

Ruby and js appear to be using regular json de-serialization.
    for (const line of lines) {
      this.push(this.fromObject(JSON.parse(line)))
    }

          io.each_line do |json|
            m = Cucumber::Messages::Envelope.from_json(json)
            yielder.yield(m)
          end

For go we'll need:
https://godoc.org/github.com/golang/protobuf/jsonpb#Unmarshaler

I implemented #959 before I saw this fix. Closing this one as my implementation also includes tests (and fixes Go)

No problem. I thought I needed a backwards compatible version of messages to get some CCK stuff to work for jvm v6 but i got it to work with the latest.


Make public enums into structs or hide them (part 1)

Part of https://github.com/apple/swift-distributed-actors/issues/999

Downing and OpLog LGTM, the Event I guess we may need to do the terrible approach instead... :-/
One day we'll get better enums in swift, like the stdlib has... but until then we have the hack heh :\

Flaky https://github.com/apple/swift-distributed-actors/issues/971


verify gives error

Whenever I try to use .verify() it gives error. But, on the other hand, I can do queries and all other stuff!

Hi @iamhssingh,
Could you please post the stacktrace?
Thanks,
Joohwan

@joowani I think I just found the error. Client.verify() only works for root user!
client = arango.ArangoClient(username='testuser', password='testadmin')
client.verify()
Traceback (most recent call last):
  File "<input>", line 1, in <module>
  File "/home/iamhssingh/PycharmProjects/VirtualEnv/lib/python3.4/site-packages/arango/client.py", line 89, in verify
    raise ServerConnectionError(res)
arango.exceptions.ServerConnectionError: [HTTP 401] Unauthorized

Ah I see. I find it rather strange that root access is required for simply asking for the version. I will keep this in mind and update the documentation. Thanks!
Best,
Joohwan

Updated the docstring for the method in https://github.com/joowani/python-arango/commit/da5d30876a226ecdd8e442f39b4c76de411394ea. Closing ticket.

@joowani Isn't it wrong? I mean, to check if Arango is working fine and then continue with the stuff what should be done then?
Also, how can I contribute in your project?

@iamhssingh Hmm you bring up an interesting point actually. It seems the Java driver ran into a similar issue: https://github.com/arangodb/arangodb-java-driver/issues/114.
I will need to make some changes to the python-arango API so all the methods in ArangoClient are also in Database level. So if you are using a non-root user, you would end up having to do something like this:
client = arango.ArangoClient(username='user', password='pass')
client.database('database_which_user_has_access_to').verify()

I will make the changes in the next release. For now, you can do a workaround something like this:
client = arango.ArangoClient(username='user', password='pass')
client.database('database_which_user_has_access_to').properties()  # use this as a ping check for now

Unfortunately this is the best we can do as this is the limitation of ArangoDB REST API (python-arango is just a wrapper around it). I will push the next release sometime this weekend.
Thanks,
Joohwan

Oh and as for contributing after the next release I will create a development branch, which you can fork and send pull requests to. Thank you for the interest!

@joowani Sure. Thanks a lot!

Hi @iamhssingh
I've made the changes in https://github.com/joowani/python-arango/releases/tag/3.8.0. Now you should be able to call verify() using another database. I've also made a development branch where you can make pull requests to: https://github.com/joowani/python-arango/tree/dev. Feel free to re-open this issue if you find any problems.
Thanks,
Joohwan


Registers package with the sunpy packaging

@samaloney the error on the py312 build related to the polarization check on the ilofar search, i think its as simple as
        if len(pol) == 1:
            pol = pol[0].upper()
            mask = mask & query_response["Polarisation"] == pol

but I wanted to check

Yea that should work 👍  I'm now questioning if that code even makes sense but that's another issue altogether ☹


Homebrew fails on builds because of being removed from Ubuntu runners

Reference - https://github.com/actions/runner-images/issues/6283 and https://github.com/Homebrew/actions/tree/master/setup-homebrew
- name: Set up Homebrew
  id: set-up-homebrew
  uses: Homebrew/actions/setup-homebrew@master

Add GitHub actions workflows that use brew install will need to be updated with this.


Bug: incorrect JSON serialization on FieldElement

So when working on #62 I found out about a critical bug on the FieldElement type that's basically breaking all contract deployments and calls. This code doesn't work:
let num = FieldElement::from_hex_be("0x1").unwrap();
let text = serde_json::to_string(&num).unwrap();
assert_eq!(text, "\"1\"");

Fails with:
thread 'tests::test_json_ser' panicked at 'assertion failed: `(left == right)`
  left: `"\"0\""`,
 right: `"\"1\""`', starknet-ff/src/lib.rs:450:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Looks like checked_rem on crypto_bigint::U256 is causing the issue. It's returning 0 for the operation.


feat(forge): get-solc command

Closes #7656
Motivation
Introduces forge get-solc <path> to get the solc version for that particular path.
This command can be useful to check compatible solc for different folders in a large project.
Solc 0.8.22

In case of multiple solcs:
Solcs 0.8.21, 0.8.22, 0.8.24

It works even if you give a file path like src/test/Test.sol.

@mattsse leave your review when you're free. ref https://github.com/foundry-rs/foundry/pull/7696#discussion_r1569968048. Thanks!


fix(dependencies): update deps. fix bug on setup

This fixes some issues surfaced by @alvincrespo and fixes a bug with versioning the project.
Changes

bump react-navigation
bump react-native-gesture-handler
remove detox in favor of manual setup later
commit project to git before setting the version
commit a second time after version has been set

Screenshots

Checklist

[ ] Automated tests
[x] Creating a new project still works
[ ] Added docs

Looks good, I ran into a weird issue at first with Android.
When running android I received this error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
Resolved with:

Installing the gradle CLI: brew install gradle

https://docs.gradle.org/current/userguide/installation.html

Generating the gradle wrapper: cd android && gradle wrapper

https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:adding_wrapper

Cleaning the Android project: ./gradlew clean & cd ../
Re-running the RN Android project: react-native run-android

This could simply be a localized issue, however I'm documenting here in case any others hit the same snag with this template after this PR is merged. Could be beneficial for a secondary check on someone else machine just in case.

Looks good, I ran into a weird issue at first with Android.
When running android I received this error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
Resolved with:

Installing the gradle CLI: brew install gradle

https://docs.gradle.org/current/userguide/installation.html

Generating the gradle wrapper: cd android && gradle wrapper

https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:adding_wrapper

Cleaning the Android project: ./gradlew clean & cd ../

Re-running the RN Android project: react-native run-android

This could simply be a localized issue, however I'm documenting here in case any others hit the same snag with this template after this PR is merged.
Could be beneficial for a secondary check on someone else machine just in case.

Ran a second check: Same deal, need to generate the gradle wrapper. Could be related to RN Version, doubtful due to change diff this PR introduce it. Merging.


Where conversion

See #986. Adds one extra method and test. cc @jmdeldin

That one failure is due to memory issues in JRuby, not a reflection of any changes in the code, so I'm going to merge this. @jmdeldin, thanks for the help with this!


Can you explain a little more about what this tool can do?

It seems to be focused on PDF text extraction rather than include any Office file logic... Is it anything you use yourself still?

Hi! This project is intended as a computational aid for manual pdf translation. The first goal would be to have a simple, yet useful way to look up the original sentences of the pdf and associate it with its translation in whatever other language you are translating to.
It is incomplete. Right now it only extracts pdf text and separate it into sentences which are shown to the user.
I might pick up on this project sometime but I have no plans to work on it anytime soon. :/
Maybe you can find some parts useful to you. Specially if you are into Haskell.


alibabacloud: Support instance-tags-filter

Please review per commit
alibabacloud: Support instance-tags-filter

/test

@pippolo84 Thanks for the review! I have addressed the comments, please take another look

/test


Fix/overlapping of bboxes

This PR implements two major changes:

Replaces detectron2 with Yolox_quantized as default model
Introduces an algorithm for reducing the overlapping in the elements detected by any model. As a benefit of these now is possible to detect more diverse element types.
Adds a property to Rectangle class to register the origin of the data.
Adds functionality to annotate function, to skip elements of certain origins
Adds functionality to annotate function to print additional details of bounding boxes
Tests updates

The changes made could be tested using the script:
https://gist.github.com/benjats07/dd7b4857a2fbf9ad49a61b609515be9e
(Notice that on the current version, this script doesn't draw elements coming from OCR.)
And the documents (need to be stored at the same location as the script):
https://drive.google.com/drive/folders/1ZsAcraXx5AzfFa9EPjm_IJ6my-2WdJl5?usp=sharing
Is recommended to run this script twice: once with the unstructured-version in this PR and again with the version in the main branch. After execution, you can check the results in the OUT folder with the following meaning:
[document-number]-[num page]-[model-name]-[old|new].png
where old indicates that the image is generated by the main version and new indicates output by this PR.
In the -new images you will notice that there aren't any elements inside others.
You can also note that some elements are missing on -new images, this is because all elements not coming from a detection model are being skipped from drawing.

confirming there is a great reduction in deuplicated boxes but also observing a few interesting differences that might be a regression in detecting certain types of elements (so far found code block and footer/header elements)


Strings for user and item IDs

Hi there,
Currently it is not possible to use User IDs other than integers,
for example 8b3876c0-69b5-444e-9118-c5fcd575169f, cannot be converted with str.Atoi(), which results in an error.
Is it possible to support strings for IDs?
Cheers,

Thanks for your feedback. The string type seems more general. I will make it work but need some time. :smile:

The issue has been addressed by #24 .


Standardize the parameter names for the API functions

Unify the API parameters' names
In certain functions, like vDataFrame.score(), the method parameter has been modified to metric. To maintain consistent parameter names and their intended meanings, I propose updating the following functions where I believe parameter names might need to be changed:

acf
corr
pacf

It seems well known API uses 'method' parameter for correlation, I close this issue.


termbox: 1.1.2 -> 1.1.3

Repointing repo to termbox/termbox as nsf/termbox is no longer maintained.

Motivation for this change
Update version and repo location
Things done

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

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

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

How do we know that's the new canonical/established location?

I looked around a bit and

freebsd ports just moved it to the new repo: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249672
termbox-haskell was moved under github.com/termbox by its author
the new termbox/termbox maintainer already contributed to he project before the fork and maintains a text editor based on termbox that's packaged on many distros

So I guess that's enough for trust, but it doesn't seem to be that established yet (for example of the two dependent packages in nixpkgs, only one points to the fork)

Hi @fgaz yes I am working to recentralize development at termbox/termbox and avoid fork hell. I updated FreeBSD last week and will be updating Alpine and Debian next. If you'd like I can send you a copy of the email I sent to the termbox community a few months ago.

Hi @adsr, thanks for chiming in (and for your work on a new central source of course)!

If you'd like I can send you a copy of the email I sent to the termbox community a few months ago

If it isn't a problem please do

@fgaz :+1: I forwarded a copy to the email address on your github profile.
Thanks for the review.

Hello. Can someone add a hacktoberfest-accepted label to this issue so that it counts toward Hacktoberfest?

I have no power to do that, sorry
(But I do have some hacktoberfest-tagged repos 🙂)

Result of nixpkgs-review pr 99581 run on x86_64-linux 1

3 packages built:

mle
nimmm
termbox

Fails to build on darwin:
these derivations will be built:
  /nix/store/qdh2rvwkm08sln5hq90wn21a3s8662ps-termbox-1.1.3.drv
building '/nix/store/qdh2rvwkm08sln5hq90wn21a3s8662ps-termbox-1.1.3.drv'...
unpacking sources
unpacking source archive /nix/store/nm569bqm38wnn9wdwl72ykwdk5jflrzc-source
source root is source
patching sources
configuring
no configure script, doing nothing
building
build flags: SHELL=/nix/store/k89nm2jva0qmvd970f84wq2iq1iwm9bs-bash-4.4-p23/bin/bash prefix=/nix/store/d4lqkg71vi739sg9b8a5ybfdrkljx33h-termbox-1.1.3
clang -c -std=c99 -Wall -Wextra -pedantic -Wno-unused-result -fPIC -g -O3 -D_XOPEN_SOURCE  termbox.c -o termbox.o
clang -c -std=c99 -Wall -Wextra -pedantic -Wno-unused-result -fPIC -g -O3 -D_XOPEN_SOURCE  utf8.c -o utf8.o
ar rcs libtermbox.a termbox.o utf8.o
clang -shared -Wl,-h,libtermbox.so.1 termbox.o utf8.o -o libtermbox.so.1.0.0
ld: unknown option: -h
clang-7: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Makefile:20: libtermbox.so.1.0.0] Error 1
builder for '/nix/store/qdh2rvwkm08sln5hq90wn21a3s8662ps-termbox-1.1.3.drv' failed with exit code 2
error: build of '/nix/store/qdh2rvwkm08sln5hq90wn21a3s8662ps-termbox-1.1.3.drv' failed

Hello, can someone try building with this patch?
https://github.com/termbox/termbox/commit/4235e57bb447b7df053cc07354577f406476c646
I don't have a mac to test with. If it looks ok I can tag as 1.1.4 or add a patch here.

Hello, can someone try building with this patch?
termbox/termbox@4235e57
I don't have a mac to test with. If it looks ok I can tag as 1.1.4 or add a patch here.

I don't have the time to test this. Can you just mark it broken on darwin?

Build passes on a fastmac vm[1]
https://github.com/fastai/fastmac

Build passes on a fastmac vm[1]
https://github.com/fastai/fastmac

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 99581 run on x86_64-darwin 1

2 packages failed to build and are new build failures:

mle: log was empty
nimmm: log was empty

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 99581 run on x86_64-darwin 1

2 packages failed to build and are new build failures:

mle: log was empty
nimmm: log was empty

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 99581 run on x86_64-linux 1

3 packages built:

mle
nimmm
termbox

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 99581 run on x86_64-linux 1

3 packages built:

mle
nimmm
termbox

darwin:
builder for '/nix/store/z2hb4y38h0iaym72wy21hma4pq3kpmci-termbox-1.1.3.drv' failed with exit code 2; last 10 log lines:                                                                       no configure script, doing nothing                                                                                building                                                                                build flags: SHELL=/nix/store/4n2ah3plbfnfz14wrzmz1pkfw78y9kz4-bash-4.4-p23/bin/bash prefix=/nix/store/frn8mfax71715zlipw8zxchy9ka20lh2-termbox-1.1.3
  clang -c -std=c99 -Wall -Wextra -pedantic -Wno-unused-result -fPIC -g -O3 -D_XOPEN_SOURCE  termbox.c -o termbox.o
  clang -c -std=c99 -Wall -Wextra -pedantic -Wno-unused-result -fPIC -g -O3 -D_XOPEN_SOURCE  utf8.c -o utf8.o
  ar rcs libtermbox.a termbox.o utf8.o
  clang -shared -Wl,-h,libtermbox.so.1 termbox.o utf8.o -o libtermbox.so.1.0.0
  ld: unknown option: -h
  clang-7: error: linker command failed with exit code 1 (use -v to see invocation)
  make: *** [Makefile:20: libtermbox.so.1.0.0] Error 1

darwin:
builder for '/nix/store/z2hb4y38h0iaym72wy21hma4pq3kpmci-termbox-1.1.3.drv' failed with exit code 2; last 10 log lines:                                                                       no configure script, doing nothing                                                                                building                                                                                build flags: SHELL=/nix/store/4n2ah3plbfnfz14wrzmz1pkfw78y9kz4-bash-4.4-p23/bin/bash prefix=/nix/store/frn8mfax71715zlipw8zxchy9ka20lh2-termbox-1.1.3
  clang -c -std=c99 -Wall -Wextra -pedantic -Wno-unused-result -fPIC -g -O3 -D_XOPEN_SOURCE  termbox.c -o termbox.o
  clang -c -std=c99 -Wall -Wextra -pedantic -Wno-unused-result -fPIC -g -O3 -D_XOPEN_SOURCE  utf8.c -o utf8.o
  ar rcs libtermbox.a termbox.o utf8.o
  clang -shared -Wl,-h,libtermbox.so.1 termbox.o utf8.o -o libtermbox.so.1.0.0
  ld: unknown option: -h
  clang-7: error: linker command failed with exit code 1 (use -v to see invocation)
  make: *** [Makefile:20: libtermbox.so.1.0.0] Error 1

I see that 1.1.4 is out

Superseded by https://github.com/NixOS/nixpkgs/pull/113831


Collaboration Sudoku

Hi Michel thank you for Sudocle.
I do Cracking the Cryptic sudokus with a friend and was wondering if it would be possible to have a collaborative sudoku app, similar to Excalidraw https://excalidraw.com/ https://github.com/excalidraw/excalidraw
Do you think it would be quick to get a proof of concept using websockets? And do you think this a feature that would best be developed for Sudocle? Is the official Cracking The Cryptic Web App not open source?

Hi Alex! This is definitely an interesting idea! Sudocle is developed with Next.js (https://nextjs.org/), which has a server that could be used to share data between computers. I'm currently exporting static HTML, so there's no server involved, but it would be a great weekend project to investigate how Next.js can be used for this and to implement a prototype. What is your plan? Would you like to implement this yourself or do you want me to do it?

Is the official Cracking The Cryptic Web App not open source?

I'm afraid not. There is no repository on GitHub (or anywhere else) and it does not have an open source license.


drivers: eth: add driver for ENC424J600 Ethernet Controller

Add driver for ENC424J600 Ethernet Controller.
Patches for the reel board and zperf sample (b54a3e6 and 17118bf)  are just for testing because the expansion boards still not ready yet.

@tbursztyka @jukkar I added patch for ENC424J600 based shield, please revise, thanks


Added GPU memory reservation image

For testing purposes: https://hub.docker.com/r/raalsky/gpu_memory_reservation

@grzegorz-gutowski


[BUG] Error when predicting from (T)BATS when the forecasting horizon is longer than the time series used in training

Describe the bug
In sktime 0.9.0 there is an error, when predict function is called on a fitted (T)BATS model in case when forecast horizon is longer than the time series used for training. This is purely sktime-related, since the forecasts from _forecaster are still possible.
To Reproduce
from sktime.forecasting.tbats import TBATS
from sktime.forecasting.bats import BATS
from statsmodels.tsa.arima_process import arma_generate_sample

# dummy time series for predictions - length 50
y = pd.Series(arma_generate_sample([2], [2], (50, 1)).flatten())
tbats_model = TBATS()  # the same for BATS
tbats_model.fit(y=y)

tbats_model.predict(np.arange(1, 10))  #OK
tbats_model.predict(np.arange(1, 25))  #OK
tbats_model.predict(np.arange(1, 50))  #OK
tbats_model.predict(np.arange(1, 51))  #OK
tbats_model.predict(np.arange(1, 52))  #ERROR (forecast horizon of 51 steps)
tbats_model._forecaster.forecast(52) #OK

Expected behavior
Well, no error I guess.
Additional context
Error message:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
~\AppData\Local\Temp\4/ipykernel_24092/2542756290.py in <module>
----> 1 tbats_model.predict(np.arange(1, 52))

c:\<hidden>\.venv\lib\site-packages\sktime\forecasting\base\_base.py in predict(self, fh, X, return_pred_int, alpha, keep_old_return_type)
    195         # this is how it is supposed to be after the refactor is complete and effective
    196         if not return_pred_int:
--> 197             y_pred = self._predict(
    198                 self.fh,
    199                 X=X_inner,

c:\<hidden>\.venv\lib\site-packages\sktime\forecasting\base\adapters\_tbats.py in _predict(self, fh, X, return_pred_int, alpha)
    125             lower = pd.Series(out["lower_bound"])
    126             upper = pd.Series(out["upper_bound"])
--> 127             pred_int = self._get_pred_int(lower=lower, upper=upper)
    128
    129         else:

c:\<hidden>\.venv\lib\site-packages\sktime\forecasting\base\adapters\_tbats.py in _get_pred_int(self, lower, upper)
    186             pred_int["idx"].isin(fh_out.to_indexer(self.cutoff).values)
    187         ]
--> 188         pred_int.index = fh_out.to_absolute(self.cutoff)
    189         pred_int = pred_int.drop(columns=["idx"])
    190         return pred_int

c:\<hidden>\.venv\lib\site-packages\pandas\core\generic.py in __setattr__(self, name, value)
   5476         try:
   5477             object.__getattribute__(self, name)
-> 5478             return object.__setattr__(self, name, value)
   5479         except AttributeError:
   5480             pass

pandas\_libs\properties.pyx in pandas._libs.properties.AxisProperty.__set__()

c:\<hidden>\.venv\lib\site-packages\pandas\core\generic.py in _set_axis(self, axis, labels)
    668     def _set_axis(self, axis: int, labels: Index) -> None:
    669         labels = ensure_index(labels)
--> 670         self._mgr.set_axis(axis, labels)
    671         self._clear_item_cache()
    672

c:\<hidden>\.venv\lib\site-packages\pandas\core\internals\managers.py in set_axis(self, axis, new_labels)
    218
    219         if new_len != old_len:
--> 220             raise ValueError(
    221                 f"Length mismatch: Expected axis has {old_len} elements, new "
    222                 f"values have {new_len} elements"

ValueError: Length mismatch: Expected axis has 1 elements, new values have 51 elements

Versions

System:
python: 3.9.5 (tags/v3.9.5:0a7dcbd, May  3 2021, 17:27:52) [MSC v.1928 64 bit (AMD64)]
executable: c:<hidden>.venv\scripts\python.exe
machine: Windows-10-10.0.18363-SP0
Python dependencies:
pip: 21.3.1
setuptools: 56.0.0
sklearn: 0.24.2
sktime: 0.9.0
statsmodels: 0.12.1
numpy: 1.19.3
scipy: 1.7.3
Cython: 0.29.25
pandas: 1.2.5
matplotlib: 3.5.1
joblib: 1.0.1
numba: 0.54.1
pmdarima: 1.8.2
tsfresh: None

hmm, how weird!
Seems to come from the ForecastingHorizon.
I guess we need to check what fh_out ends up being, it seems to be a valid ForecastingHorizon object, but to_absolute breaks.
We'll look at this in the next batch of bugfixes.
Until then, would appreciate if someone could try reproduce and/or check what fh_out is before it breaks.

yes, reproduced, including that it happens precisely under the condition stated (forecasting horizon is longer than training series)

@ k1m190r, would this perhaps also be addressed by the bugfix in #1842?
It seems like it might be the same cause.

Unable to reproduce the bug anymore. Apparently changes in 0.10.* have fixed this :) @Garrus990. Can you please upgrade to current and see if you still get an error.

I was checking in the version 0.10.0 and the error is no more. Let me close then the issue :)


Is there a "hosted" version of this anywhere?

If not, do you need hosting or something?

Also, it's a bit different but I am using this on https://kitnic.it.

Hey @mithro, as @kasbah said, I'm working on a client-side version (to work like svgerber) and a server-side gerber-rendering-as-a-server. The client-side one is coming along (and will likely be GH Pages or S3), but the server-side one is little more than a proof of concept on my machine (and the reason the tracespace org exists).
I need more free time most of all! But some infrastructure would be good, as well. Haven't crunched any numbers, but (eventually) was hoping to throw it all up on AWS free-tier and see if I could ride that out. Did you have something specific in mind?

We've added the sites using this section in the readme with some places this library is being used. Otherwise, there's some plans in store for tracespace. If you're interested in contributing in any way, please reach out!


org.scalajs.jsenv.ComJSEnv$ComClosedException: Phantom.js isn't connected

phantomjs version: 1.9.7
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
When building on developer boxes we are able to use phantom js just fine, however on our jenkins build server we get the following stack trace:
[error] (pint-sjs/test:loadedTestFrameworks) org.scalajs.jsenv.ComJSEnv$ComClosedException: Phantom.js isn't connected
[error] Total time: 11 s, completed Jan 14, 2015 5:40:07 PM
orange:pint-sjs:2.2.13-SNAPSHOT> last pint-sjs/test:loadedTestFrameworks
[debug] PhantomJS WS Jetty: INFO: jetty-8.1.16.v20140903 WrappedArray()
[debug] PhantomJS WS Jetty: INFO: Started {} WrappedArray(SelectChannelConnector@localhost:32847)
[debug] PhantomJS using webpage launcher at: /tmp/phantomjs-launcher-webpage3086986974158994472.html
[debug] PhantomJS using launcher at: /tmp/phantomjs-launcher1638445151149022404.js
org.scalajs.jsenv.ComJSEnv$ComClosedException: Phantom.js isn't connected
	at org.scalajs.jsenv.phantomjs.PhantomJSEnv$ComPhantomRunner.receive(PhantomJSEnv.scala:234)
	at org.scalajs.testadapter.ScalaJSFramework.fetchFrameworkInfo(ScalaJSFramework.scala:60)
	at org.scalajs.testadapter.ScalaJSFramework.<init>(ScalaJSFramework.scala:29)
	at org.scalajs.sbtplugin.ScalaJSPluginInternal$$anonfun$40$$anonfun$apply$29.apply(ScalaJSPluginInternal.scala:453)
	at org.scalajs.sbtplugin.ScalaJSPluginInternal$$anonfun$40$$anonfun$apply$29.apply(ScalaJSPluginInternal.scala:452)
	at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
	at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244)
	at scala.collection.immutable.Map$Map1.foreach(Map.scala:109)
	at scala.collection.TraversableLike$class.map(TraversableLike.scala:244)
	at scala.collection.AbstractTraversable.map(Traversable.scala:105)
	at org.scalajs.sbtplugin.ScalaJSPluginInternal$$anonfun$40.apply(ScalaJSPluginInternal.scala:452)
	at org.scalajs.sbtplugin.ScalaJSPluginInternal$$anonfun$40.apply(ScalaJSPluginInternal.scala:437)
	at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47)
	at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:40)
	at sbt.std.Transform$$anon$4.work(System.scala:63)
	at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
	at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:226)
	at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:17)
	at sbt.Execute.work(Execute.scala:235)
	at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
	at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:226)
	at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:159)
	at sbt.CompletionService$$anon$2.call(CompletionService.scala:28)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

This is still on 0.6.0-M3, I will try RC1 next, but I suspect it will still be a problem because i don't know what would have changed on the scalajs/sbt side to fix this.

One thing to keep in mind is that our build server where we are seeing this issue is significantly slower than our dev boxes. So if there is a race to connect to the socket, that might be the source of the problem. I see that commit fdc8c5a42d4c408549101a01a0db9a1fa0876060 might help in that regard if I understand it correctly.

Still getting these with 0.6.4 quite often.

The workaround so far is to use this when running on your CI:
set inScope(ThisScope in theScalaJSProject)(
    postLinkJSEnv := new org.scalajs.jsenv.RetryingComJSEnv(PhantomJSEnv().value))

This is what do here.
We still don't have a clue what causes this, unfortunately :-(

@benjaminjackman Is this still an issue, or can we close this?

Unfortunately I can't say I stopped using it.

@benjaminjackman Is this still an issue, or can we close this?

Unfortunately I can't say I stopped using it. It's fine to close from my perspective.

OK let's close this, then, thanks.


only connect to api.mangadex.org using https

Neko (v<IP_ADDRESS>) curently try's to connect to http://api.mangadex.org getting a http/301 back and redirects to https://api.mangadex.org with every request.
Only connecting to https will speed up the communication with mangadex, and also increase security because Neko also sends it's mangadex session cookie plaintext over the air/internet with it's http request.

good catch


[POC] Secure media (simple version)

What is the context of this PR?
Describe what you have changed and why, link to other PRs or Issues as appropriate.
How to review
Testing parenting of images when creating a NEW page

In Wagtail, add a new "Information Page" to somewhere in the page tree.
Use "Image upload test" for the title and "Test" for summary.
For the "Content" field, add an "Image" block and click "Choose an image" to open the chooser modal.
Click on the "Upload" tab in the modal to access the 'create' form.
Inspect the form code using dev tools and look for the hidden fields. You should see the following set of hidden field values (because the page doesn't have an ID yet, but we DO know the content-type):

image-chooser-upload-parent_object_content_type should have a value
image-chooser-upload-parent_object_id should NOT have a value
image-chooser-upload-parent_object_id_outstanding should have the value True

Complete the form to upload a new image and click the "Upload" button.
In a new tab, go to the 'Images' library and edit the image you just added.
Inspect the edit form code using dev tools and look for the hidden fields. The field values should reflect those seen in modal form (The ID of the parent page is still not known, but the content type is).
Switch back to the original tab, then click "Save draft" at the bottom of the page.
Switch back to the "Edit image" tab and REFRESH the page.
Inspect the form code using dev tools and look for the hidden fields once more. Now that the ID of the parent page is known, the parent_object_id field should have a value reflective of the newly saved page, and parent_object_id_outstanding should now have a value of 'False'.

NOTES
When the ID of the parent is not yet known, media must be marked in such a way that keeps it 'private' in the immediate term, and the ID should be set once it is known. When media-containing pages are first saved, a signal handler looks for any 'unparented' media added within the last 1 hour by the same user, for a page with the same content type, and backfills the missing data.
POTENTIAL ISSUES
If the editor fails to hit "Save draft" within the 1-hour time-frame, and creates and saves a page of the same time within the same hour, that media could be parented to the wrong page! Thoughts on how to address this are welcome :) I don't think we can comb the reference index first time round, because it isn't populated until afterwards.
Testing parenting of images when editing an existing page

In Wagtail, edit the draft page you created in the previous section.
For the "Content" field, add a new "Image" block and click "Choose an image" to open the chooser modal.
Click on the "Upload" tab in the chooser modal to access the 'create' form
Inspect the form code using dev tools and look for the hidden fields. You should see the following set of hidden field values:

image-chooser-upload-parent_object_content_type should have a value
image-chooser-upload-parent_object_id should match the current page ID
image-chooser-upload-parent_object_id_outstanding should have the value False

Complete the form to upload a new image and click the "Upload" button.
In a new tab, go to the 'Images' library and edit the image you just added.
Inspect the edit form code using dev tools and look for the hidden fields. The field values should reflect those seen in modal form.

NOTES
When the ID of the parent known, media can be tied to the object immediately, allowing the 'privacy' to immediately reflect that of the current page (if the current page is live, the media can be public, otherwise, it is private).
Testing parenting of documents when creating a NEW page

In Wagtail, add a new "Information Page" to somewhere in the page tree.
Use "Document upload test" for the page title and "Test" for the summary.
For the "Content" field, add an "Documents" block, then click the "+" symbol to add a "Document", then "Choose a document" to open the chooser modal.
Click on the "Upload" tab in the chooser modal to access the 'create' form.
Inspect the form code using dev tools and look for the hidden fields. You should see the following set of hidden field values (because the page doesn't have an ID yet, but we DO know the content-type):

document-chooser-upload-parent_object_content_type should have a value
document-chooser-upload-parent_object_id should NOT have a value
document-chooser-upload-parent_object_id_outstanding should have the value True

Complete the form to upload a new document and click the "Upload" button.
In a new tab, go to the 'Documents' library and edit the document you just added.
Inspect the edit form code using dev tools and look for the hidden fields. The field values should reflect those seen in modal form (The ID of the parent page is still not known, but the content type is).
Switch back to the original tab, then click "Save draft" at the bottom of the page.
Switch back to the "Edit document" tab and REFRESH the page.
Inspect the form code using dev tools and look for the hidden fields once more. Now that the ID of the parent page is known, the parent_object_id field should have a value reflective of the newly saved page, and parent_object_id_outstanding should now have a value of 'False'.

Testing parenting of documents when editing an existing page

In Wagtail, edit the draft page you created in the previous section
For the "Content" field, use the "+" action to add a new "Document" to the existing "Documents" block and click "Choose a document" to open the chooser modal.
Click on the "Upload" tab in the modal to access the 'create' form
Inspect the form code using dev tools and look for the hidden fields. You should see the following set of hidden field values

document-chooser-upload-parent_object_content_type should have a value
document-chooser-upload-parent_object_id should match the current page ID
document-chooser-upload-parent_object_id_outstanding should have the value False

Complete the form to upload a new document and click the "Upload" button.
In a new tab, go to the 'Documents' library and edit the document you just added.
Inspect the edit form code using dev tools and look for the hidden fields. The field values should reflect those seen in modal form.

Testing image privacy for a draft page

In Wagtail, edit the draft "Image upload test" page created earlier and open the preview pane.
Inspect the HTML where the image appears.
Because the page is still a draft, the src value of the rendition should be something like /images/{secure key}/2/original/{image filename}.
Open this URL in a new tab.
Sign out of Wagtail.
Switch to the 'Image URL' tab you opened in step 4.
Refresh the page. You should get a "403 Forbidden" response.
In a new tab, Sign back in to Wagtail.
Refresh the 'Image URL' tab once more, and you should see the generated rendition again.

NOTES
Images added to draft pages set their is_private field value to True on save. Where the storage backend supports it the original file AND the files for any renditions generated from it it will also be set to 'private', preventing both direct and indirect access. However, you won't be able to see this locally. Whilst an image is private, renditions are served by a 'Serve' view, which only responds to authenticated users with some level of permission for the image (by default, this is based on the 'collection' the image belongs to).
Testing image privacy once a draft page has been published

In Wagtail, edit the draft "Image upload test" page again, and publish it.
In the green success message on the next page, click the "View live" button to view the live/public-facing version of the page.
Inspect the HTML for the image. The src value should look something like: media/images/{image filename}.fill-446x390.format-webp-.original.png.
Access Wagtail again edit the "Image upload test" page once more.
Open the preview pane and inspect the HTML for the image there too. The src value should look the same as it did on the live version.
At the bottom of the page, click the arrow next to the "Save draft" button to view the additional options, and click "Unpublish page".
On the confirmation screen, click "Yes, unpublish it" to confirm the action.
Edit the page again in Wagtail and look again at the preview pane.
Inspect the HTML for the image once more. The src value should now again look like: /images/{secure key}/2/original/{image filename}.

NOTES
When a page with child media is published, signal handlers detect this and trigger updates to any private media items, resulting in their is_private flag being set to False, and the permissions on files themselves being set to 'publically readable' (where the storage backend supports it).
When a live page is unpublished, signal handlers again detect this and trigger updates to any public media items, resulting in their is_private flag being set to True, and the permissions on the files themselves being set to 'private' again (where the storage backend supports it). To allow editors to still see the images in the preview pane, we rely again on the 'Serve' view to serve image renditions, so that only authenticated users with some level of permission on the image can see it.
POTENTIAL ISSUES

It's currently possible for pages to reuse images uploaded for other pages, in which case, that media will only become public once the official parent page is published (potentially leaving a published page displaying a mix of 'public' and 'private' media). In reality, this is only likely to happen between pages that are part of the same 'bundle', so the pages (and by extension, their child media) should be published more-or-less simultaneously. However, we might want to think about solutions here (e.g. the media being 're-parented' to the page that was published first).
We need to review this behaviour more closely in environments where edge-level caching is involved. It's likely that more work will be needed to submit purge requests for certain URLs.

Next steps

[ ] Update documentation
[ ] Ensure python manage.py retry_file_permission_set_attempts is set to run on a cron every 10 minutes in all target environments

On review, I've come to a conclusion that:

'Media permissioning' (in Wagtail) and 'Media privacy' (what end-users can see) are two separate things, and this PR perhaps unnecessarily conflates the two things
Whilst the parent -> child association is useful from the perspective of 'Media permissioning' (which editors have permission to see/use/edit it in Wagtail), I don't think it's something we need to tie directly to the 'privacy' of the image.
When it comes to 'Media privacy' (what end-users can see), I think things can be simpler: The media is always 'private' on upload, and only becomes 'public' on page publish when the media is actually present in the revision being published.

@MebinAbraham / @zerolab Will close this now, as it's superseded by #46 and #48


Readme image asset

Hi,
GitHub had a bit of a hissy fit with the readme image asset, here's the image that was in there.

Fixed in https://github.com/Jarhead20/RRPathGen/commit/f69c2da5d11b4d2d7c6841aae2d4c09cc12bb57d


Error while building within micro_ros_setup

Hi
Today I tried building this library for galactic. More specifically, the un-string-ify branch.
The steps to reproduce are...
source install/setup.sh
ros2 run micro_ros_setup create_firmware_ws.sh generate_lib generic

# clone diagnostics
cd firmware/mcu_ws && git clone -b feature/un-string-ify https://github.com/micro-ROS/micro_ros_diagnostics.git
cd ../..

# Copy colcon.meta and toolchain
cp -R external/ros-embedded-interfaces/* firmware/mcu_ws
rm -rf firmware/mcu_ws/ros2/rosidl/rosidl_typesupport_introspection_c/
rm -rf firmware/mcu_ws/uros/micro_ros_utilities/
ros2 run micro_ros_setup build_firmware.sh $(pwd)/external/uros.CMakeLists.txt $(pwd)/external/colcon.meta

When building the library,
/gcc-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/9.3.1/../../../../arm-none-eabi/bin/ld: cannot find -ldl
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/example_website_checker.dir/build.make:117: example_website_checker] Error 1
make[1]: *** [CMakeFiles/Makefile2:85: CMakeFiles/example_website_checker.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
/gcc-arm-none-eabi/bin/../lib/gcc/arm-none-eabi/9.3.1/../../../../arm-none-eabi/bin/ld: cannot find -ldl
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/example_processor_updater.dir/build.make:117: example_processor_updater] Error 1
make[1]: *** [CMakeFiles/Makefile2:112: CMakeFiles/example_processor_updater.dir/all] Error 2
make: *** [Makefile:144: all] Error 2
---
Failed   <<< micro_ros_diagnostic_updater [3.04s, exited with code 2]

I think it's due to note, I have been using this setup to build the micro-ros library, including custom messages we have without any issue. Furthermore, the dl library is only needed for dynamic memory, which shouldn't be needed. We do get the typical warning https://github.com/micro-ROS/freertos_apps/issues/37, but this never caused problems.
Maybe there's some flag missing?
@pablogs9 maybe you've seen this before?

Here's my colcon.meta (maybe helps to replicate).
{
    "names": {
        "tracetools": {
            "cmake-args": [
                "-DTRACETOOLS_DISABLED=ON",
                "-DTRACETOOLS_STATUS_CHECKING_TOOL=OFF",
            ]
        },
        "rcl": {
            "cmake-args": [
                "-DBUILD_TESTING=OFF",
                "-DRCL_COMMAND_LINE_ENABLED=OFF",
            ]
        },
        "rcutils": {
            "cmake-args": [
                "-DENABLE_TESTING=OFF",
                "-DRCUTILS_NO_FILESYSTEM=ON",
                "-DRCUTILS_AVOID_DYNAMIC_ALLOCATION=ON",
                "-DconfigUSE_POSIX_ERRNO=1",
                "-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON",
                "-DRCUTILS_NO_64_ATOMIC=ON",
            ]
        },
        "microxrcedds_client": {
            "cmake-args": [
                "-DUCLIENT_PIC=OFF",
                "-DUCLIENT_PROFILE_UDP=ON",
                "-DUCLIENT_PROFILE_DISCOVERY=OFF",
                "-DUCLIENT_PROFILE_SERIAL=OFF",
                "-DUCLIENT_PROFILE_TCP=OFF",
                "-DUCLIENT_PROFILE_MULTITHREAD=ON",
            ]
        },
        "rmw_microxrcedds": {
            "cmake-args": [
                "-DRMW_UXRCE_MAX_NODES=7",
                "-DRMW_UXRCE_MAX_PUBLISHERS=5",
                "-DRMW_UXRCE_MAX_SUBSCRIPTIONS=15",
                "-DRMW_UXRCE_MAX_SERVICES=1",
                "-DRMW_UXRCE_MAX_CLIENTS=0",
                "-DRMW_UXRCE_MAX_HISTORY=8",
                "-DRMW_UXRCE_TRANSPORT=udp",
                "-DRMW_UXRCE_DEFAULT_UDP_IP=<ip>",
                "-DRMW_UXRCE_DEFAULT_UDP_PORT=8888",
            ]
        }
    }
}

It seems that you are trying to build an executable here and the generate_lib tries to build just libraries.
Could you try to make this executable conditional at CMake level and also make it disabled by default?

Thanks for your feedback, @bjv-capra. Do you think we should add some of these aspects to the docs?
Also I think I should get rid of the example updaters in the updater package or at least make them a cmake option?


the root domain name of the notion sharing page has changed

https://twitter.com/NotionHQ/status/1415370771623333889

Looking a bit into this, seems that new pages made public have a new attribute requireInterstitial in their state.
This will then go and render a message that you might see like
Continue to external site by following the link below
Old published page publicPageData:
{
betaEnabled: false
canJoinSpace: false
canRequestAccess: false
publicAccessRole: "reader"
requireLogin: false
spaceDomain: "redacted"
spaceId: "redacted"
spaceName: "redacted"
userHasExplicitAccess: false
}

New published page publicPageData:
{
betaEnabled: false
canJoinSpace: false
canRequestAccess: false
icon: "https://lh3.googleusercontent.com/a-/AOh14GghnUZUM7qD1l5Bvbvs308TIw-0B74qCVE4wLED4Q=s100"
publicAccessRole: "reader"
requireInterstitial: "https://random.notion.site/My-page-randomPageId"
requireLogin: false
spaceDomain: "redacted"
spaceId: "redacted"
spaceName: "redacted"
userHasExplicitAccess: false
}

publicPageData seems to be the server side props that notion server pass to the frontend. Not sure if that might be the case of some similar case I experience creating a new page with the new "domain updates".

I just tried creating a page today and get the error you describe here with the page just showing "Continue to external site by following the link below".
Is there is a manual edit that can be made to the fruitionsite script?

I tried to cuild my site today. I did not see the message "Continue to external site by following the link below" but a login page showed up.

A hacky way is to intercept the "/api/v3/getPublicPageData" request from the edge worker and change the retrieved payload by removing the requireInterstitial attribute.

Could you please provide more details on how to do this?

Fruition dosen't work  on Iphone 5s  .Tried on Safari and Chrome ,on two different mobiles and no content display .Before Notion update, sites  was displaying ok .

I try to use the latest codes but it still unsuccess.My codes provide via the
https://hkusts.notion.site/Fruition-Problem-b163c070b7c94f1ea6f6ddbf1d8a466a

🙁 yes confirm. not working. pls provide update if there is a chance that is going to work again. trusted some sites to this solution, if no future, than have to go for alternatives. thx a lot.

So what I can do now is to wait?


Failed assertion: line 110 pos 12: '_positions.isNotEmpty'

I have 5 pieces of data in my Swiper, I have an Index record of the current position, and when I delete the last item, I move the Index forward and delete the last item. This is when the error is reported.
flutter: The following assertion was thrown:
flutter: ScrollController not attached to any scroll views.
flutter: 'package:flutter/src/widgets/scroll_controller.dart':
flutter: Failed assertion: line 110 pos 12: '_positions.isNotEmpty'
flutter:
flutter: Either the assertion indicates an error in the framework itself, or we should provide substantially
flutter: more information in this error message to help you determine and fix the underlying cause.

As a test, swiperlayout. DEFAULT appears when layout is selected

I only can use DEFAULT layout. This bug should be fixed, please do it.

If don't set index, it's ok!

Swiper(             loop: false,             itemBuilder: (BuildContext context, int index) {               return Center(                   child: Image.file(                 _imageList[index],                 fit: BoxFit.fill,               ));             },             itemCount: _imageList.length,             index: _index == widget.initialIndex ? _index : null,             onIndexChanged: (index) {               setState(() {                 _index = index;               });             },           ),

    Swiper(
        loop: false,
        itemBuilder: (BuildContext context, int index) {
          return Center(
              child: Image.file(
            _imageList[index],
            fit: BoxFit.fill,
          ));
        },
        itemCount: _imageList.length,
        index: _index == widget.initialIndex ? _index : null,
        onIndexChanged: (index) {
          setState(() {
            _index = index;
          });
        },
     )

Working , thanks brother


Scan barcode become very small (after v3.1.0 update, have picture and ccde)

after i upgrade the library from libary 3.0.3@arr to 3.2
the problem raise when i use the below code in a lenovo pad
code base

the problem is that i can use the scan function as the view do not inflate correctly.

There are a few different scaling options you can try, details here: https://github.com/journeyapps/zxing-android-embedded/blob/master/EMBEDDING.md#notes-on-scaling


Update zlib to version 1.2.12 to resolve CVE-2018-25032

According to CVE-2018-25032 (link) zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.
Fix was committed to zlib GitHub here: https://github.com/madler/zlib/commit/5c44459c3b28a9bd3283aaceab7c615f8020c531
zlib source should be updated to 1.2.12

This is being tracked in the private modules repo - https://github.com/microsoft/cpp_client_telemetry_modules/issues/183


Documentation check + update

This PR is consists of a very large number of documentation fixes. Some of these for minor bugs/problems, but most of these are making the docs less specific to the SAFE project.
As part of this I made a safedata at SAFE page. At the moment it does feel like a slightly random collection of information, so let me know if you have any suggestions for improvements there.
Also @davidorme, I add two TODOs in docs/using_safedata/overview.md to create/extend the use case recipes for uploading non-Excel files, and to update an existing data set. I don't know if they should be added onto this PR, but think they should be done before the release of 3.0.0

Codecov Report

Merging #79 (8add629) into release/3.0.0 (b5b021a) will not change coverage.
The diff coverage is 0.00%.

@@              Coverage Diff               @@
##           release/3.0.0      #79   +/-   ##
==============================================
  Coverage          69.00%   69.00%
==============================================
  Files                 12       12
  Lines               3639     3639
==============================================
  Hits                2511     2511
  Misses              1128     1128

Impacted Files
Coverage Δ

safedata_validator/entry_points.py
0.00% <0.00%> (ø)

safedata_validator/taxa.py
87.65% <ø> (ø)

safedata_validator/zenodo.py
0.00% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Cengage Logo needs to be updated

Description:
Cengage Logo needs to be updated to new 'Cengage Group' logo
Steps to reproduce the behavior:

Launch https://storybook-preview-319--upbeat-sinoussi-f675aa.netlify.app/?path=/story/fileuploader--no-limits
Go to 'Patterns'
Click on 'Logo'

Actual Behavior:
Old Cengage Logo is displayed
Expected behavior:
New "Cengage Group" Logo should be displayed
Screenshots
https://screencast-o-matic.com/watch/cr6jDtVXqcF
Desktop (please complete the following information):

OS: [win 10]
Browser [chrome]
Version [94.0.4606.81 (Official Build) (64-bit)]

I don't really think this is a bug.  "Cengage Group" is a separate entity from "Cengage".  "Cengage" represents the Higher Ed side of the business so this logo is still valid.  And since the logo part of the Header Pattern is just a place where you can put any logo, I don't think it really matters which one we put in the demo.  The component itself is not broken.


Fix minor tslint rules and add guide how to run tests

Fix tslint rules according to #113 . Update README to indicate how to run tests.

👍


/src/count.cc can silently drop input files

At l.299 a file reader gets silently deleted if reader::getFileReader() fails (at least when it does at l.192 in /include/reader.h).
I noticed this happening, because i increased ip_files limit/capacity too get around issue 42 and actually added an output at l.299 in count.cc.
In my particular case the number of (bz2 compressed) files i gave to squeakr count exceeded the configured maximum allowed open file count (ulimit -n).  So after reaching that limit fopen() fails (after adding onother output - with "too many open files").
In that case (and from what i understand in every other case that would prevent a file from beeing opened) false is returned and the file reader just gets deleted. With nothing really indicating that this is happening!
I cant see any difference in reader.h l.184, l.187 (and l.198) so i think with plain fastq and gz compressed input the same could happen (but i havent tested it).
I think a warning output or even an error should be the response of count.cc after the delete at l.299 (maybe the error from fopen() would be nice too).
If i get the chance i will test if i can trigger this by just removing the reading rights of an input file.
Sincerely
tkranz

I checked with input files for which i removed the reading rights and as expected the silent drop happens with those as well.
I append a zip containing a git patch (fix#43.patch) for this. With that, a warning gets issued when squeakr count drops a file and reader.h prints the actual error with perror().
fix#43.zip


export model on every checkpoint + log printing update

--logs now only print throughput one
--on every checkpoint, an exported model is made. Last n models are kept
as backups.

Per conversation, going to close this PR and open new ones for the eval/checkpoint and less hooks for single node training.


Crashing on firebase::app::Create

[REQUIRED] Step 1: Describe your environment

Xcode version: 11
Firebase C++ SDK version: v6.12.0
Firebase IOS SDK version: v6.33.0
Firebase Component: Firebase Crashlytics (Firebase Analytics)
Installation method: Zip file

[REQUIRED] Step 2: Describe the problem
Сrash on start with container-overflow in Firebase C ++ wrapper.
Steps to reproduce:
==546==ERROR: AddressSanitizer: container-overflow on address 0x000118109a40 at pc 0x0001122191d8 bp 0x00016ae39030 sp 0x00016ae387c0
WRITE of size 159 at 0x000118109a40 thread T0
    #0 0x1122191d4 in wrap_memmove
    firebase/firebase-ios-sdk#1 0x106e85788 in std::__1::vector<char, std::__1::allocator<char> >::vector<char const*>(char const*, std::__1::enable_if<(__is_forward_iterator<char const*>::value) && (is_constructible<char, std::__1::iterator_traits<char const*>::reference>::value), char const*>::type)
    firebase/firebase-ios-sdk#2 0x106e851c4 in firebase::app_common::RegisterLibrariesFromUserAgent(char const*)
    firebase/firebase-ios-sdk#3 0x106e868f8 in firebase::App::RegisterLibrary(char const*, char const*)
    firebase/firebase-ios-sdk#4 0x106e84840 in firebase::app_common::AddApp(firebase::App*, std::__1::map<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, firebase::InitResult, std::__1::less<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > >, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const, firebase::InitResult> > >*)
    firebase/firebase-ios-sdk#5 0x106e86714 in firebase::App::Create(firebase::AppOptions const&, char const*)
    firebase/firebase-ios-sdk#6 0x106e85f04 in firebase::App::Create()
    firebase/firebase-ios-sdk#7 0x10569349c in -[GameDelegate application:didFinishLaunchingWithOptions:]

Rerouted to Firebase C++ Issue list since the backtrace is all C++.

Hi @VGolets,
I couldn't reproduce this issue locally on my machine. I built the analytics quickstart example with the following settings,

Built directly pointing to the latest firebase source SDK

cmake -G Xcode -S . -B build -DFIREBASE_CPP_SDK_DIR=~/firebase/firebase-cpp-sdk<EMAIL_ADDRESS>
cmake --build build -j8

Copy a google-services.json file into the executable directory
./build/Debug/desktop_testapp

Built with prebuilt firebase libraries 6.11.0

cmake -G Xcode -S . -B build_prebuilt_6.11.0 -DFIREBASE_CPP_SDK_DIR=~/firebase/prebuilt/firebase-cpp-sdk
cmake --build build_prebuilt_6.11.0

Built with prebuilt firebase libraries 6.15.1

cmake -G Xcode -S . -B build_prebuilt_6.15.1 -DFIREBASE_CPP_SDK_DIR=~/firebase/prebuilt/firebase-cpp-sdk
cmake --build build_prebuilt_6.15.1

All of the cases above worked as expected.
Could you please try running the quickstart example and let us know if its not working? It will be great to reproduce this bug locally.

Another thing that might not work is the combination of C++ SDK and iOS SDK here.
The iOS SDK that is being used (v6.33.0) is too recent.
Our prebuilt libraries were built and tested with following iOS SDK versions,
FIrebase C++ SDK -> Firebase iOS SDK
6.16.0 -> 6.32.2
6.12.0 -> 6.16.0


fix: adding file name validation before adding file to database (upload image)

This PR does the same thing as #103 , but for the image upload route

Thx


httplib_fc() is not thread safe

All function calls use the same static structure.

Fixed in https://github.com/lammertb/libhttp/commit/8118c908eb644a507a11710baf9f0cbda49c0edc by removing the function and passing the context and connection independently to httplib_cry(). This is a better solution because in practice you can have errors on a context without a connection, but it is impossible to have an error on a connection without a context because all connections are operating in a context. (at least that should be the case, but practice is somewhat different).


Generate CSV data per Spark version for tools [databricks]

Fixes #10424.  Adds CSV generation per Apache Spark version under tools/generated_files.  The existing CSV files for tools data has been preserved to avoid breaking downstream pipelines that use this data.  Once those pipelines have been updated to consume the new per-Spark versions of these files, we can remove the old tools CSV files.

build

build

build


Branch for  Swift 1.2

I'm using this as a submodule in a project, but we won't be migrating to Swift 2.0 for awhile. How about a branch for 1.2?

I'll jus make a temp copy until we move to 2.0. Seems easier that way with Xcode 6 server's sensitivity to branches anyway.


silence unused warning on MSVC

@scoder this revives #4149 since I forgot (yet again) how to restore a deleted branch from a PR. I am pretty sure you or @da-woods already explained me how this can be done ...
This implementation uses code.insertion_point as suggested by @da-woods to place function calls behind the variable declarations for C89.
After this the remaining usages of CYTHON_UNUSED are:
static CYTHON_UNUSED PyObject* __Pyx_Method_ClassMethod(PyObject *method);
static CYTHON_UNUSED int __Pyx_PyType_Ready(PyTypeObject *t);
static CYTHON_UNUSED double __Pyx__PyBytes_AsDouble(PyObject *obj, const char* start, Py_ssize_t length) {

This converts:
CYTHON_UNUSED int a = 0;

void func(CYTHON_UNUSED int a) {}

to
int a = 0;
CYTHON_UNUSED_VAR(a);

void func(int a) {CYTHON_UNUSED_VAR(a);}

this should work for any compiler. For >=C++17 or >= C23 the previous approach would allow the usage of the attribute: maybe unused
#define CYTHON_UNUSED [[maybe_unused]]
CYTHON_UNUSED int a = 0;
void func(CYTHON_UNUSED int a) {}

@scoder this is ready for review

@scoder after thinking about this again, maybe the following implementation is more appropriate:
#ifndef CYTHON_UNUSED_VAR_DECL
# if defined(__GNUC__)
#   if !(defined(__cplusplus)) || (__GNUC__ > 3 || (__GNUC__ == 3 && __GNUC_MINOR__ >= 4))
#     define CYTHON_UNUSED_VAR_DECL(statement) __attribute__ ((__unused__)) statement;
#   else
#     define CYTHON_UNUSED_VAR_DECL(statement)  statement;
#   endif
# elif defined(__ICC) || (defined(__INTEL_COMPILER) && !defined(_MSC_VER))
#   define CYTHON_UNUSED_VAR_DECL(statement) __attribute__ ((__unused__))  statement;
# elif defined(_MSC_VER) && _MSC_VER >= 1500
#   define CYTHON_UNUSED_VAR_DECL(statement) \
      __pragma(warning(push)) \
      __pragma(warning(disable:4101)) \
      statement; \
      __pragma(warning(pop))
# else
#   define CYTHON_UNUSED_VAR_DECL(statement) statement;
# endif
#endif

int main()
{
    CYTHON_UNUSED_VAR_DECL(int i);
    return 0;
}

I think it would be fine to have these warning for ancient msvc versions

Using __pragma or since C++11/c99 _Pragma might be a good solution for constant expression warnings as well.

    CYTHON_UNUSED_VAR_DECL(int i = 5);
    CYTHON_UNUSED_VAR_DECL(int b) = 5;

I'd rather not mix this into arbitrary statements. Having a separate marker 'command' feels better to me.

I think it would be fine to have these warning for ancient msvc versions

Users of old compilers can probably live with those, as long as their code works.

I'd rather not mix this into arbitrary statements. Having a separate marker 'command' feels better to me.

what do you mean with separate marker 'command'

I'd rather not mix this into arbitrary statements. Having a separate marker 'command' feels better to me.

what do you mean with separate marker 'command'

I meant the CYTHON_UNUSED_VAR() markers, whose sole purpose is to say "this is unused" and nothing more. Sorry for being unclear.

@scoder do we still want to get the other changes here in? I could get them finished, but I am unsure whether the warnings are worth the trouble. At this point they only affect msvc with C or <C++17. Since I am likely going to start using C++17 soon they will not affect me personally anymore.
I only see the following ways to fix this:

generate them at the same place but add an extra insertion point as argument to the function
implement this using additional functions, which means they are generated in a different place to the condition
generate them in place using some kind of atrocity

#if defined(__cplusplus) || (defined(__STDC_VERSION__) && __STDC_VERSION__ >= 199901L)
#define CYTHON_UNUSED_VAR_IN_DECL(var) (void)var;
#else
#define CYTHON_UNUSED_VAR_IN_DECL(var)
#endif

int func(CYTHON_UNUSED int arg1, int arg2)
{
    int var1 = arg2;
    CYTHON_UNUSED_VAR_IN_DECL(arg1);
    int var2 = arg2;
    return var1 + var2;
}

Version 1) was my initial implementation in https://github.com/cython/cython/pull/4693/commits/b4a266489979e65c61756fe941daee6a6c4b162a, but @da-woods was unhappy with the additional function argument. Version 2) is the revised implementation, but I agree that it is not great to have them defined in different places.
I am happy to go ahead in whichever way you deem best, or drop this completely if you think this is just not worth the extra maintenance effort.

From my pov this is not really worth these changes, so closing this for now


Pagination number is not visible

This is a(n):

[ ] Update to an existing Animated Button
[x] Any Error
[ ] Proposal to the Repository
[ ] Documentation / README.md changes

Details:

in dark mode the number in pagination is not visible clearly. I would like to work on this issue under GSSoc23. Can you assign it to me?

Hi, are you still working on this issue? If you've already made a PR with the changes that have been merged then please close the issue. If you have an open PR, please mention this issue number in your PR in order to link them.

@PoorviShetty Someone has already solved this issue before i start.


Documentation example components

Coverage remained the same at 100.0% when pulling 152558e964d84c4d46f2349f700678e3ab6d5380 on documentation-example-components into b4b1f5d80ca844d32d1aeaa612aef780f9afac41 on dev.


Please support BATS 1.2.0?

BATS 1.2.0 came out in April - would you mind pushing an updated image please? https://github.com/bats-core/bats-core/releases/tag/v1.2.0

cc @toolmantim @lox

I just looked into this for you @petemounce, but I believe this is blocked on https://github.com/bats-core/bats-core/issues/315#issuecomment-629806607 — when that's resolved, we can cut a new version of plugin-tester that depends on it!

Ah, thanks very much for checking.
(I'm trying to find out where this load.bash is coming from (where BATS_PATH is, in the image), or whether that is optional, for work I'm doing adding some tests to https://github.com/seek-oss/docker-ecr-cache-buildkite-plugin/pull/26 .)

Sounds like some hairy debugging!
BATS_PATH is defined here: https://github.com/buildkite-plugins/buildkite-plugin-tester/blob/master/Dockerfile#L35
But I think you can leave out the load "$BATS_PATH/load.bash" line from your bats tests, and things will still work? 🤔

It turned out that I was struggling with the fact that on my Windows host, CRLF line-endings. Inside the linux container, LF is the expectation. So, yeah, tripped over cross-platform stuff 💯 for the win! Sorted now, and filed seek-oss/docker-ecr-cache-buildkite-plugin#27 for what I hope is a better fix.

Sounds annoyingly tricky! Glad you got it sorted, and thanks for contributing that PR. I’ll leave this open tho, to track the BATS 1.2.0 upgrade 👍🏼

Hey folks! We are going to work on upgrading to BATS 1.5 (it's in our backlog). Feel free to create a PR 🙏🏻

I'm going to reopen this one so we can track it 😊 At the moment the version of BATS is 1.5 and the plan is to upgrade it to that one. No ETA yet, but if you want to create a PR for this, we'll make sure the review it as soon as possible!

This was done in #44 with the BATS 1.7.0 upgrade 👍🏼


Url Annotation is buggy

Is this a Bug or Feature request?:
Bug
Steps to reproduce (preferably a link to a GitHub repo with a repro project):
Create a Model with a Single Property string, annotate it with [Url] and a View with a input that binds the value of the input to the model.
Now type as Url:
https://httpsblabla
Description of the problem:
See the ModelState beeing valid.
Version Microsoft.AspNetCore.All:
2.0.5

Thanks for contacting us, @Kris0.
Can you please share a repro project for us to investigate (ideally as a github repo).
@dougbu, can you please investigate this? Thanks!

Seems related: https://github.com/aspnet/Mvc/issues/8381

@Kris0 the [Url] attribute is not part of ASP.NET Core. Instead, it ships with .NET Framework and .NET Core.
I believe .NET has had issues related to this attribute rejecting valid URLs. At the moment, the .NET Core version does little more than confirm the value starts with a recognized scheme. Suggest using a [RegularExpression] attribute with the patterns your application supports (though this has performance implications). The .NET Framework version may be more complicated.
By the way, https://httpsblabla is a completely valid URL on a private network.
FYI the .NET Core source is found here.

Thank you for the information. I already use [RegularExpression] in my projects instead of the [URL] or the [EmailAddress] annotations. Yes you are absolutely right, https://httpsblabla is a valid URI in a private network but i think most people would assume we talk about absolute addresses in the www if we see the annotation URL. Maybe it should be renamed in URI ? (or maybe that's just my opinion?)


Add constants for 'rc'

Just like we have dev, testing, and release constants, I think it makes sense to have rc constants which submit shorter proofs, have lower file limits, use less hosts, etc. Then we don't have to switch up the constants every time we want to release an rc, we can just know that we've got functional rc constants.

Jordan and I were discussing this, and it occurred to me that the constants we want to change usually depend on what functionality was introduced by the RC. So I'm not sure that hardcoding RC constants makes sense.

Some of them you probably want to change regardless. For example, you want the upload times to be short enough that you can get a full upload cycle through (with renewing and whatnot) before the full release is out.
That's the only major one I can think of off the top of my head, but I'm guessing that if we were to go through the full list of constants we'd find a few other things that everyone would agree should be changed for all rc releases.


Add format script

Add a script to format Polygolf source (the script would call the normalize function).

Comments should be added to the AST to be preserved.


Inf evaluator

Remove AccumulateNoInf
Add InvalidEvaluatorException
AbstractIntegrator::LLs(Mutation) will invalide an Evaluator that returns -inf and throw an InvalidEvaluatorException
Polish can catch InvalidEvaluatorException and retry mutation finding with smaller list of Evaluators; in this case, Polish will warn via std::cerr.
Polish::ConsensusQuality(ai) skips over InvalidEvaluatorExceptions

In looking at this, I think we are hampered by the lack of API documentation on the AbstractIntegrator. So, for example, I think some of the changes here change the API contract, but it's unclear because there is no API contract.

As to the substance of the commit... I'm still thinking about it

This definitely implements what we discussed: the sanest most conservative approach for how we should address this possibility.
I'm not sure we should be creating temporary std::vectors only to accumulate them afterwards -- I'm not confident they'll be elided away entirely, it may have a performance impact (presently testing mutations does no allocation that I'm aware of). We might want a private function that does both via returning the sum and supporting per-eval LLs via an output parameter std::vector* and if !nullptr, clears, reserves, and fills it.

This is mainly a POC that what we discussed works. I wasn't prepared that you rip the core of CC2 apart, because it lacks logging, contracts, and documentation. Of course I'm changing the contracts, as it is required. I'd prefer @dalexander puts this as a story into jira and split it there.


fix(config): make metrics_level opt backward compatible

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Type of metrics-level has been changed from int to enum recently.

This PR adds backward compatibility for metrics-level in cli opt and env var. It parses 0 as disabled and 1 as info.
This PR removes unnecessary --metrics-level from docker compose files.
This PR doesn't add the backward compatibility for metrics-level in toml file, because it requires to implement Deserialize for MetricLevel, which is verbose and not necessary, because rarely MetricLevel will be explicitly set in toml file.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

Customize clap::ValueEnum::from_str for MetricLevel won't work, because EnumValueParser never call it.


[a11y] keyboard interaction and tooltype

According to http://www.w3.org/TR/wai-aria-practices/#tabpanel
Escape key shoud dismiss the tooltip.

Is this for the tooltip? Please put more detailed information when opening issues.

@wesleycho I think it is for tooltip:

Escape key shoud dismiss the tooltip.

Linking this for reference: http://www.w3.org/TR/wai-aria-practices/#tooltip
In particular, this requires tooltips being tracked in a global data store - $$stackedMap from the modal service needs to be used, so that needs to be separated into a new module.


Simplify the rubocop exclusions for test dirs

Signed-off-by: Tim Smith<EMAIL_ADDRESS>

@tas50 i hate that clicking update branch breaks this

If that's the thing that breaks the DCO check we can ignore it.

Also any test contribution is DCO free since it doesn't touch intellectual property.