Update cats-core to 2.0.0-RC1

Updates org.typelevel:cats-core from 2.0.0-M4 to 2.0.0-RC1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "org.typelevel", artifactId = "cats-core" }]

labels: semver-pre-release

Codecov Report

Merging #128 into series/0.7.x will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           series/0.7.x     #128   +/-   ##
=============================================
  Coverage         61.18%   61.18%
=============================================
  Files                11       11
  Lines               304      304
  Branches              8       11    +3
=============================================
  Hits                186      186
  Misses              118      118

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 0803d8e...9e4fb6f. Read the comment docs.


Thank you! I wasted hours trying to make bootable ESXi 6.6 USB

I had wasted hours trying to make bootable ESXi 6.6 USB using other guides I found.
Holding down Option key and rebooting MacMini did NOT show the USB device until I used your guide.

Guides that used dd command did NOT work.
The guide below did NOT work for me on ESXi and MacMini:

How to create a bootable VMware ESXi USB drive on Macs

Your guide worked great!

Press power and immediately and hold down Option key
Select the yellow and aluminum EFI boot disk and install ESXi

Thank you for sharing your work!

👍 from me too. thanks so much!!

Worked great- thanks!

Estutton,  Thank you, thank you, thank you.  What a pain this was up to this point.  Thank you!!!

@rreichel002 I am glad this issue helped you find the fix from @cbednarski
My manager approved purchase of a VMware vSphere Essentials Kits.  Now I must figure this out all over again and hope my MacMini host host will be happy.
I will keep the USB @cbednarski helped make in case I must roll-back!

Thanks

Thank you

Thanks @cbednarski ! Surprisingly this still works like a champ burning ESXi 7.0.2 via a Monterey computer.


NameError: name 'unicode' is not defined

After updating from 0.5.0 to 0.6.1 using Python 3.4, I get this error:
  File "/home/abadaba/dev/activities/lib/python3.4/site-packages/stravalib/model.py", line 233, in AthleteStats
    recent_ride_totals = EntityAttribute(ActivityTotals)  #: Recent totals for rides. (:class:`stravalib.model.ActivityTotals`)
  File "/home/abadaba/dev/activities/lib/python3.4/site-packages/stravalib/attributes.py", line 245, in __init__
    super(EntityAttribute, self).__init__(*args, **kwargs)
  File "/home/abadaba/dev/activities/lib/python3.4/site-packages/stravalib/attributes.py", line 37, in __init__
    self.type = type_
  File "/home/abadaba/dev/activities/lib/python3.4/site-packages/stravalib/attributes.py", line 258, in type
    if isinstance(v, (str, bytes, unicode)):
NameError: name 'unicode' is not defined

I found this in StackOverflow (http://stackoverflow.com/questions/19877306/nameerror-global-name-unicode-is-not-defined-in-python-3), so by simply removing the unicode check in line 258 (only checking for (str, bytes)) works and all my tests pass (not sure whether this will brake anything, though).
If you think it's ok, I'll do the PR

I can fix this. It should be using six. Not sure how that got through, must
have been an accidental merge from a recent PR.
On Wed, Aug 31, 2016, 00:51 Daniel<EMAIL_ADDRESS>wrote:

After updating from 0.5.0 to 0.6.1 using Python 3.4, I get this error:
File "/home/abadaba/dev/activities/lib/python3.4/site-packages/stravalib/model.py", line 233, in AthleteStats
recent_ride_totals = EntityAttribute(ActivityTotals)  #: Recent totals for rides. (:class:stravalib.model.ActivityTotals)
File "/home/abadaba/dev/activities/lib/python3.4/site-packages/stravalib/attributes.py", line 245, in init
super(EntityAttribute, self).init(*args, **kwargs)
File "/home/abadaba/dev/activities/lib/python3.4/site-packages/stravalib/attributes.py", line 37, in init
self.type = type_
File "/home/abadaba/dev/activities/lib/python3.4/site-packages/stravalib/attributes.py", line 258, in type
if isinstance(v, (str, bytes, unicode)):
NameError: name 'unicode' is not defined
I found this in StackOverflow (
http://stackoverflow.com/questions/19877306/nameerror-global-name-unicode-is-not-defined-in-python-3),
so by simply removing the unicode check in line 258 (only checking for (str,
bytes)) works and all my tests pass (not sure whether this will brake
anything, though).
If you think it's ok, I'll do the PR
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hozn/stravalib/issues/90, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAX7Ay1ftNj5wBYH7dgi7wFDsO1s57hxks5qlTKOgaJpZM4JxU_B
.

This should be fixed now in just-pushed 0.6.2.  Unit tests pass on python 3 (3.5) and python 2, so I think we're good.  Sorry about that!

Thx! it works now!


Flow opaque type alias backport

Q
A

Bug fix?
no

Breaking change?
no

New feature?
yes

Deprecations?
no

Spec compliancy?
yes

Tests added/pass?
yes

Fixed tickets
N/A

License
MIT

Backported version of #643. Flow opaque type aliases.
Turns out 6.x did not have support for parsing "declare export" outside of a module, so I had to add that here, too. Vast majority of this code is copypasta from master.

@hzoo, mind taking a look?

You've got a test/fixtures/flow/opaque-type-aliases/declare_opaque/.actual.js.swp file in here, probably didn't intend to commit that?

Oops-- removed! Thanks :)

@hzoo @existentialism - is there anything I can do to help this get reviewed? Facebook needs this (and the babel backport) before we can use opaque types internally :/
Or is something going on with 6.x? Like you don't want to merge things into it anymore?

Nothing going on, just don't have anyone doing backports/releases

@gabelevi we're focused (if I can even really say that for an open source project) on releasing 7 so hope it makes sense that we haven't really been looking into backports, etc.

Also as long as y'all are around when it's released to fix issues 👍 , that's a concern of mine too

Thank you! Definitely happy to fix any issues that come up

https://github.com/babel/babylon/releases/tag/v6.18.0


Add more file conflict options

What feature or improvement do you think would benefit Files?
please allow more option when conflicting files occur:

add a "integrate option" for folders if the folder to be pasted exists (like windows explorer)
add "date comparison" option if files already exists to choose which one to keep (with option to keep booth)
add option to compare other file details

Requirements

adding above mentioned features

Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22000.1281
Windows Version
Windows 11
Comments
No response

Folder are already merged when it already exists

It would also be nice if the Windows 7 style option to keep both file versions of the same name without comparing them first was added.

Merging with #9803


Improvements to convert for pmac

@gilesknap this makes convert run and do ~sensible things for pmacController. It doesn't yet keep hold of the macros. I will investigate what the consequences of that might be.

OK, nice.  pmacController converts fine.
Now I'm having a go at an axis.
Please could we get this error
AssertionError: Can't find device class and parent class in header file

To print the names of the things it can't find?

I don't suppose pvi knows about the motor record?
pvi convert device /workspaces/ioc-pmac/ibek-support/motor  /epics/support/motor/motorApp/MotorSrc/asynMotorController.h  --template /epics/s
upport/motor/db/basic_asyn_motor.db
Traceback (most recent call last):

  File "/workspaces/pvi/src/pvi/_convert/_asyn_convert.py", line 61, in asyn_component_type
    return record_types[self.type]

KeyError: 'motor'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):

  File "/venv/bin/pvi", line 8, in <module>
    sys.exit(app())

  File "/workspaces/pvi/src/pvi/__main__.py", line 103, in device
    component_group = TemplateConverter(templates).convert()

  File "/workspaces/pvi/src/pvi/_convert/_template_convert.py", line 32, in convert
    self.templates, self._extract_components()

  File "/workspaces/pvi/src/pvi/_convert/_template_convert.py", line 43, in _extract_components
    component = parameter.generate_component()

  File "/workspaces/pvi/src/pvi/_convert/_asyn_convert.py", line 119, in generate_component
    asyn_cls = self.write_record.asyn_component_type()

  File "/workspaces/pvi/src/pvi/_convert/_asyn_convert.py", line 63, in asyn_component_type
    raise KeyError(

KeyError: " asyn type motor({'DESC': '$(DESC)', 'DTYP': '$(DTYP)', 'DIR': '$(DIR)', 'VELO': '$(VELO)', 'VBAS': '$(VBAS)', 'ACCL': '$(ACCL)', 'ACCU': '$(ACCU=0)', 'BDST': '$(BDST)', 'BVEL': '$(BVEL)', 'BACC': '$(BACC)', 'OUT': '@asyn($(PORT),$(ADDR))', 'MRES': '$(MRES)', 'PREC': '$(PREC)', 'EGU': '$(EGU)', 'DHLM': '$(DHLM)', 'DLLM': '$(DLLM)', 'INIT': '$(INIT)', 'TWV': '1'}) not found in['ao', 'bo', 'busy', 'longout', 'mbbo', 'stringout']"

[pmac](convert-name-handling)[pvi]$

I still think we should merge this by the way. It is a big improvement to the convert process.

To print the names of the things it can't find?

It doesn't currently know the classes. That is why it is searching for a specific pattern. We could just provide the device and parent class on the command line, perhaps optionally, but I think it would still make sense to try to verify that those classes are correct. Maybe the pattern is still too strict? What is the class definition in this case?

KeyError: 'motor'

I think this is just because motor records just aren't implemented currently.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (b7ee8e9) 89.01% compared to head (c0f749e) 89.08%.

Files
Patch %
Lines

src/pvi/_convert/_asyn_convert.py
80.00%
1 Missing :warning:

src/pvi/_convert/_template_convert.py
50.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #84      +/-   ##
==========================================
+ Coverage   89.01%   89.08%   +0.07%
==========================================
  Files          23       23
  Lines        1338     1338
==========================================
+ Hits         1191     1192       +1
+ Misses        147      146       -1

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


URI from object level not getting added to swagger end points.

This is the last issue then I will have the ability to generate a swagger client for qbit.


Swarm container reject incomming connection from port 20 for an FTP client in active mode

Description
The goal is to run a java FTP client in active mode inside a container on a Swarm environment.
The FTP client in active mode open a socket for data connection (on an exposed port: 21030), to get the response of a LIST command for instance.
The FTP server tries to establish connection from source port 20 but is rejected at network level.
In the test environment, the FTP server is vsftpd. When the option connect_from_port_20 is set to NO, the FTP server uses a random source port and the communication works fine.
This issue has been found on docker v1.12.3 on a RHEL 7.2 host and reproduced on docker v17.03.0-ce on a CentOS 7.3 host. The base image is a CentOS 6.8 with java-1.6.0-openjdk.x86_64 installed
Steps to reproduce the issue:

Have an FTP server that accept active mode
Run a container from CentOS 6.8 image
docker run -ti centos:6.8 bash
Install JDK
yum install -y java-1.6.0-openjdk.x86_64
Leave the container and create the container image
docker commit $(docker ps -qa) centos_jdk:6.8
Copy the joined FtpClient.jar in $HOME directory
This is a small low level FTP client used for test and written in java. It is based on org.apache.commons.net.ftp.FTPClient java API. The jar file and the corresponding sources are joined to this issue.
Start the Swarm service
docker service create -p 21030:21030 -p 21031:21031 --mount type=bind,source=$HOME,destination=/home_host -t centos_jdk:6.8 bash
Exec a bash on the the container
docker exec -ti $(docker ps -q) bash
Get the eth0 IP address, used to configure the FTP client internal bind address
ifconfig eth0 | grep "inet addr"
Get the host IP address exposed to the FTP server, used to configure the external FTP client IP
Launch the FtpClient tool
cd /home_host/
java -jar FtpClient.jar
Configure the connection
If configuration is correct, the client should be connected to the command port of the server
Launch LIST command

Describe the results you received:
The FTP server failed to establish connection
Describe the results you expected:
The LIST command should return the files list of the current FTP directory
Additional information you deem important (e.g. issue happens only occasionally):
Here some network captures
In the following, the Docker host is x.x.x.217 and the FTP server is x.x.x.211
In a simple container (launched with docker run) the connection is well established and the listing is sent.
  0.098526 x.x.x.211 -> x.x.x.217 TCP ftp-data > 21030 [SYN] Seq=0 Win=14600 Len=0 MSS=1460 TSV=2449485623 TSER=0 WS=7
  0.098691 x.x.x.217 -> x.x.x.211 TCP 21030 > ftp-data [SYN, ACK] Seq=0 Ack=1 Win=14600 Len=0 MSS=1460 WS=7
...
  0.099199 x.x.x.211 -> x.x.x.217 FTP-DATA FTP Data: 1334 bytes
  0.099320 x.x.x.211 -> x.x.x.217 TCP ftp-data > 21030 [FIN, ACK] Seq=1335 Ack=1 Win=14720 Len=0

In a container launched by a Swarm service (docker service create) the TCP packet is reset and no trace of dropped packet found
  0.230802 x.x.x.211 -> x.x.x.217 TCP ftp-data > 21030 [SYN] Seq=0 Win=14600 Len=0 MSS=1460 TSV=2449553354 TSER=0 WS=7
  0.260654 x.x.x.217 -> x.x.x.211 TCP 21030 > ftp-data [RST, ACK] Seq=1 Ack=1 Win=0 Len=0

Output of docker version:
Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 08:10:07 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 08:10:07 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 17.03.0-ce
Storage Driver: overlay
 Backing Filesystem: xfs
 Supports d_type: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: active
 NodeID: ij93zz3h4g4fam9ib55bqm8st
 Is Manager: true
 ClusterID: gjg3lppnkr6cs50yj3e2prgjb
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 977c511eda0925a723debdc94d09459af49d082a
runc version: a01dafd48bc1c7cc12bdb01206f9fea7dd6feb70
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-514.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.702 GiB
Name: sds-docker219.corp.capgemini.com
ID: SM2K:TH27:UTQQ:LOEA:EFA7:WJ5W:M6PY:OIGA:QYT7:RX6V:AQQ5:QFBC
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 40
 Goroutines: 137
 System Time: 2017-03-13T17:32:05.79351146+01:00
 EventsListeners: 1
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
The host OS is a CentOS 7.3 on a VmWare virtual machine

I can't join the jar file, so this is the java file for the FTP client.
It have to be linked with commons-io-2.4 and commons-net-3.3 to be compiled.
FtpClient.java.txt

I think in this mode the server needs to know the real IP of the client.
Does it work if you start the service in host publish mode ?
--publish mode=host,target=21030,published=21030 --publish mode=host,target=21031,published=21031

It works in host publish mode in docker 17.03, thank you
Is there any way to make it work in docker 1.12.3 as the host publish mode is not recognized in this version ?

This solution works in docker v17.03 but not in v1.12.3.

Is there any way to make it work in docker 1.12.3 as the host publish mode is not recognized in this version ?

I am afraid no, if you want to use docker service for that.
The host mode thing is available starting 1.13.0

Any clue on the port 20 as source port problem ?


modify codebase to support React 15.5 deprecations

React 15.5 deprecates createClass, PropTypes and ReactTestUtils. These need to be reflected in the codebase to avoid warnings & future incompatibility

PR #663 is tracking this.


pub global activate packages don't work with --preview-dart-2

Related to https://github.com/dart-lang/sdk/issues/32188
If I run
DART_VM_OPTIONS=--preview-dart-2 pub global run webdev build, then the dart2 flag is passed properly, and I can use dart2 features like optional new/const.
However, if I run
pub global activate webdev
DART_VM_OPTIONS=--preview-dart-2 webdev build

then the flag is not passed properly to the dart vm, so we get failures with optional new/const.

After talking with @natebosch , closing this, as it will be fixed automatically when Dart2Stable ships.


App Crashing when opening some manga

Steps to reproduce

Open Neko
Open Manga info for manga with unread chapters (doesn't seem to crash with items with no unread chapters, but not all manga with unread will cause a crash)
App crashes

Expected behavior
Should be able to open manga info without crashing
Actual behavior
App Crashes when opening manga info
Crash logs
neko_crash_logs.txt
Neko version
2.10.0
Android version
Android 11
Device
Samsung Galaxy Tab S5e
Other details
Extra Logs in case it helps:
2022-08-16-release.txt
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have tried the troubleshooting guide.
[X] I have updated the app to the newest version Latest.
[X] I have filled out all of the requested information in this form.

Dunno why but both your log files are blank

here are my crash logs for this issue
neko_crash_logs (1).txt

Dunno why but both your log files are blank

Hmm might be something with github upload because I remember there being text in them.
I'll try re-uploading them tonight after I get home from work.

@CarlosEsco Here are the logs. For some reason it keeps giving me an error when I try to upload these to the original post.
Let me know if these work for you.
neko_crash_logs.txt
2022-08-16-release.txt

I have the same issue as well on Neko 2.10.0, but on Android 10 and a Xiaomi MI8. I've noticed sometimes a message "No chapters to delete" appear at the bottom of the screen before crashing event though I didn't try to delete anything, I don't know if it can be a helpful info (I'll leave a clip of two crashes where the second shows this behaviour)
https://drive.google.com/file/d/1YH5DFQjsNOauYsUzVGzNpTVDNVD0yDCU/view?usp=drivesdk

I have the same issue as well on Neko 2.10.0, but on Android 10 and a Xiaomi MI8. I've noticed sometimes a message "No chapters to delete" appear at the bottom of the screen before crashing event though I didn't try to delete anything, I don't know if it can be a helpful info (I'll leave a clip of two crashes where the second shows this behaviour)
https://drive.google.com/file/d/1YH5DFQjsNOauYsUzVGzNpTVDNVD0yDCU/view?usp=drivesdk

No chapters deleted will be fixed in next one

thanks

@CarlosEsco Here are the logs. For some reason it keeps giving me an error when I try to upload these to the original post. Let me know if these work for you. neko_crash_logs.txt 2022-08-16-release.txt

thanks those work

@dvorak13 can you try logging out and relogging into dex.  That should fix your issue.  I'll still address the crash though

Should be fixed in <IP_ADDRESS>.  Reopen and provide new crashlogs if not

@CarlosEsco It's still crashing in the new version. Also tried relogging into MangaDex. Don't See how to reopen this issue.
neko_crash_logs.txt
2022-08-18-release.txt

@dvorak13 anyway you can join the discord channel, so we talk through more things?  The crash log isnt helping

Got something to try for next release

neko_crash_logs (2).txt
heres some more logs in case it helps

again, if this helps, I was looking for a manga to add to my library, I found one, read a chapter, and decided to add it, the moment I added it the app crashed.
neko_crash_logs (3).txt
here are some more logs

let me know if 2.10.2 fixes

Using 2.10.2 right now, and it happens with me as well... Seems to only happen when the manga is in my library
here's the log

What Manga is failing to open?  when in library?

Can you verify in the android settings that Neko has full file access permissions?

no permissions denied, full access to storage

just for clarity sake, can you logout of trackers and dex, (dont relogin) let me know if it occurs

send the crash log again if it crashes

logging out of MD fixed it.
I was tracking with MAL, but turning it back on did not cause any crashes either, so it seems to be only with mangadex

The problem seems to be with auto sync on read status, once i turned it off, logged in MD, it seemed to fix it
hope this helps ^^

if you turn it back on, does it work now that you "logged in".  I ask cause it works fine on my end but at least now i can emulate it manually

actually, forget that, it's now working perfectly fine even with everything turned on? this is very confusing

The login stuff was having issues thus the 401 error in the crash log.  I added handling for that scenario in 2.10.2 but for some reason it wasnt working for you.  I"ll have to redouble check that case

Ah, i see... Well, thank you for the help, you're doing so much for us bro!
Keep up the good work! Best of luck^^

Relogging MAL Tracking (only tracking I use) fixed it for me too.

Installed 2.10.2 and app crashed with known manga's that caused crashes before.
logged out of Dex and crashes still happen
logged into Dex and crashes still happen
logged out of MAL tracking and crashes stopped
logged back into MAL Tracking and no crash

should be resolved with 2.10.3


Add a Loading Page Instead of Simple Div for Fallback in Suspense

Is your feature request related to a problem? Please describe.
Currently, when components are being lazy-loaded in the application, the fallback UI is a simple
Loading...
. This does not provide a visually engaging experience or any indication of what is being loaded.
Describe the solution you'd like
I propose creating a dedicated loading component that provides a more visually appealing loading state. This could include a spinner, animation, or any other design element that enhances the user experience during the loading process.
Describe alternatives you've considered
One alternative is to use a third-party loading spinner library, but it may not align with the current design aesthetic of the application. Another option is to use a simple text message, but that lacks engagement.
Contributor Information
Please check if you are a contributor from:

[x] GSSoC-ext
[x] Hacktoberfest

@MihirSaiDudekula go ahead👍

I have made the following changes:
added a spinner for page loading:

and a 404 not found page

can i proceed with PR @jeevan10017 ?

please add the 'hacktoberfest' label instead of 'hactoberfest' (missing k)

@MihirSaiDudekula Can you create an attractive loading spinner that matches the theme and content? or else create this as PR.

@MihirSaiDudekula Can you create an attractive loading spinner that matches the theme and content? or else create this as PR.

Got it, I'll try a bit and get back to you
Any suggestions from your side?
How can I make it better?

fixed the color scheme

Thanks.
1 last request, kindly add 'hacktoberfest' label to the repository and 'hacktoberfest-accepted' label to this PR. since, it doesnt accept it otherwise.

@MihirSaiDudekula Thank you for the correction.😊👍
let me know if any other issues

@MihirSaiDudekula Thank you for the correction.😊👍 let me know if any other issues

Thanks a lot for the quick response! No such issues!


stg_nodes failure

Describe the bug

Steps to reproduce

run dbt build --select package:dbt_project_evaluator
all models pass except for stg_nodes
Expected results

stg_nodes builds
Actual results

Screenshots and log output

19:28:27  Postgres adapter: Postgres error: value too long for type character varying(600)
19:28:27  On model.dbt_project_evaluator.stg_nodes: ROLLBACK
19:28:27  Timing info for model.dbt_project_evaluator.stg_nodes (execute): 2023-10-27 19:28:19.945495 => 2023-10-27 19:28:27.953701
19:28:27  On model.dbt_project_evaluator.stg_nodes: Close
19:28:27  Database Error in model stg_nodes (models/staging/graph/stg_nodes.sql)
  value too long for type character varying(600)
  compiled Code at target/run/dbt_project_evaluator/models/staging/graph/stg_nodes.sql
19:28:27  Sending event: {'category': 'dbt', 'action': 'run_model', 'label': 'ffbb0816-d823-4323-9373-8f279dff1642', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x7fdcc855dd30>]}
19:28:27  8 of 61 ERROR creating sql table model wfp_dbt_dev_1.stg_nodes ................. [ERROR in 8.04s]
19:28:27  Finished running node model.dbt_project_evaluator.stg_nodes

System information
The contents of your packages.yml file:
---
packages:
  - package: dbt-labs/dbt_utils
    version: 1.0.0
  - package: dbt-labs/audit_helper
    version: 0.7.0
  - package: dbt-labs/codegen
    version: 0.9.0
  - package: dbt-labs/metrics
    version: 1.4.1
  - package: calogica/dbt_expectations
    version: 0.10.0
  - package: dbt-labs/dbt_project_evaluator
    version: 0.6.2

Which database are you using dbt with?

[ ] postgres
[x] redshift
[ ] bigquery
[ ] snowflake
[ ] trino/starburst
[ ] other (specify: ____________)

The output of dbt --version:
1.4

Additional context

Are you interested in contributing the fix?

Sure

the content of the nodes seem to hit the varchar(600) limit-- I wonder if just increasing that (which is in the cross_db_shim macros, would allow this to run?

Can you try adding a file under your macros folder setting up a higher value?
For example, like:
{%- macro redshift__type_string() -%}
  {{ "VARCHAR(5000)" }}
{%- endmacro %}

I'd also be interested in knowing what column would be more than 600 chars.

Hello, I had the same issue and @b-per solution of increasing the size of the varchar in a new file: macros/cross_db_shim/redshift_shims.sql.sql and removing the dispatch from dbt_project.yml I was able to run the stg_nodes

thanks yes, worked for me too!
On Fri, Nov 10, 2023 at 12:11 PM Reynaldo Méndez Robles <
@.***> wrote:

Hello, I had the same issue and @b-per https://github.com/b-per
solution of increasing the size of the varchar in a new file:
macros/cross_db_shim/redshift_shims.sql.sql and removing the dispatch
from dbt_project.yml I was able to run the stg_nodes
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/dbt-project-evaluator/issues/390#issuecomment-1806193313,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNOBUJIDGBMNEMK72BVCHLYDZU43AVCNFSM6AAAAAA6TIX536VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWGE4TGMZRGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks for the update!


New project root-signing-staging

As documented in https://github.com/sigstore/root-signing/issues/929 I'd like to start maintaining the staging TUF repository for root-signing with the TUF-on-CI tool. The reasons are

have a meaningful way to test architectural and process changes in root signing
If root-signing-staging works well, start maintaining the actual root-signing repository with TUF-on-CI

Currently the "staging TUF repo" is just static files within root-signing git -- a setup that doesn't really resemble production very much. The plan is to actually maintain the staging repository act more like the production one (with some changes like lower signature thresholds to keep maintenance manageable).
I plan to open some PRs to this repo and link to this issue (as I figure out Pulumi etc), but high level plan is this:

define a sigstore-rootsigning-team which could include at least @jku (me) and @kommendorkapten
define a new project root-signing-staging (I will take other name suggestions though)
Configure the GCP KMS like production root-signing, so that the new project can sign with a testing key (preferably a new one for this specific purpose)
(likely later) Configure GCS for publishing like production root-signing

cc @haydentherapper

My plan was to enable GitHub Pages publishing from Actions for the the new project (that may later be replaced by GCS publishing). However, it looks like pulumi is not capable of enabling Pages publishing from Actions. So I maye have to either workaround that (somehow?) or go straight to GCS publishing


Support for prometheus

Hi!
One question, what do you think about adding an optional object to enable the prometheus scraping of home assistant?
Something among the lines of:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  labels:
    hommeassistant: prometheus
  name: prometheus
  namespace: prometheus
spec:
  endpoints:
  - interval: 30s
    targetPort: 8321
    path: /api/prometheus
  namespaceSelector:
    matchNames:
    - homeassistant
  selector:
    matchLabels:
      homeassistant-label: "true"

If you think it's a good Idea I can create a PR if you have appetite for contribs.

Hi, thank you; that would be great. Please ensure it's as configurable as possible. For example, you can take inspiration from the Grafana Helm charts here: https://github.com/grafana/helm-charts/blob/main/charts/grafana/templates/servicemonitor.yaml.
Also, could you please include information indicating that the integration must be enabled, as detailed here: https://www.home-assistant.io/integrations/prometheus/?
Many thanks.

Hey @pajikos ! I've been crazy busy, but I was going to actually going to get to this one. Do you want to reopen this issue?


cli: perhaps insecure-skip-tls-verify shouldn't be a global flag?

It seem to me that it would be enough to specify this once at login and then remember this.
On the one hand, it's a better user experience. On the other hand, it's less in-your-face about the issue.
But even a browser only asks you only once per session if you'd like to ignore cert error for a given site...
@jessesuen wdyt?

@gdsoumya tokens don't live forever, so periodic re-authentication is required and might naturally address that concern...
Except in cases where refresh tokens are supported...
I can just make it that refresh attempts do not happen in the event that a cert warning is currently being ignored. That would force the user to re-authenticate and actively choose once again to ignore the cert issue.

What is the max ttl for the tokens kargo provides? If it's a very short period that's probably okay then btu if it's like a week or more idk I would rather not cache then.

We don't directly control it in all cases.
For admin tokens, it's configurable.
If you're using Dex, it's configurable.
If you're using OIDC with some other identity provider, it may or may not be configurable.

It seem to me that it would be enough to specify this once at login and then remember this.

Are we talking about whether or not we should remember the insecure-skip-tls-verify preference in the ~/.config/kargo? If so, then this should be fine. ~/.kube/config has a setting for this, as does Argo CD. Sometimes this is just the way folks need to operate.

deprioritizing since just a nice to have for 0.1.0.

Are we talking about whether or not we should remember the insecure-skip-tls-verify preference in the ~/.config/kargo? If so, then this should be fine.

Yes.

But the title of this is: "perhaps insecure-skip-tls-verify shouldn't be a global flag?"
I would say it should be both

I'm fine with that.


check if app's need for libssp.

This PR fix compilation at list at msys2 gcc-9.3.0 .

Info: Waiting with merge as long as travis CI is down for maintenance.

@slyshykO: Thank you for your contribution!


pagemenu-navigation Right bar button item(cannot hide according to tabs)

Hi
 i am using pagemenu in my ios project

in a viewcontroller i am having a navigation bar in which at right side i have slidemenu button and left side i have bar button item(called select photo added in storybord)
below that navigation bar i am adding pagemenu view 4 tab( contains  patient, EMR, chat, prescription)
so according to tapping i want to hide/show that bar button item(that means only for EMR tab i want to show the bar button item(select photo) otherwise i want to hide,but i cannot achieve
see the screen shot i attached

)
please any one help me on this

You can use this: https://github.com/alejouribesanchez/ScrollHideNavigationController


Codecov is still commenting on PRs 🙄

via https://github.com/urfave/cli/pull/1019#issuecomment-569253463
https://github.com/urfave/cli/pull/979 didn't work I guess 😭

We could try something like this:
https://github.com/cri-o/cri-o/blob/master/.codecov.yml
We use this config to have only a very short comment on PRs like this:
https://github.com/cri-o/cri-o/pull/3045#issuecomment-565188431

I consider this resolved now. Please holler if you think otherwise 💖


Creating a project roadmap

Hi there,
First and foremost, thank you very much for your excellent contribution to the RL community! I was wondering if it would be possible to create a simple roadmap or a to-do list as part of this repository? This list could enumerate bugs and features that are planned to be tackled or are already being tackled by your team. While I've noticed comments scattered throughout the GitHub discussions as well as in the paper, it would be immensely helpful to have a single place providing a general overview.
I believe such a roadmap could be invaluable for individuals considering using or relying on this project in their production use cases. Additionally, it would also be beneficial to those interested in contributing to the project itself (i.e., calling dibs on solving a particular thing). I would be happy to come up with an initial template and gather already open issues, in case that would help.
Cheers!

Thank you for your kind comments and great suggestion, Aleksa. We will prepare such a roadmap. There is still a lot to be done but we are working on them. Thank you.


redesign welcome page

First quick draft of the new welcome page waiting for figma public to make sure colors, spacing and responsive is good
related to #11

Don't know why the deploy preview is failing.

Hello ! Updates are done Some feedbacks: @R-mooon

windi is really great ^^
what do you mean about social text ? I have added the social to follow the design so should be good
the padding for the button I was following the figma padding (it was already 4px). I added a bit for x-
added padding on mobile on the container
Reduced margin bottom on mobile
removed shadow

@R-mooon  any updates feedbacks?

Hello sorry i was unable to respond.
Do you have a deploy preview ?

I don't know why the preview are not working properly. @pi0  @danielroe  any ideas?

Personal feedback:
Design-wise, the Previous version looks minimal, sharper, and more native-like. Buttons for social media could be added more minimally as icons-only and adding a "Join us" below them is just unnecessary information (action label could be a tooltip). Also, any reason Shadow, bolding and right line in the second box was removed?
Usability-wise, we are adding some links but they should be directly accessible from docs witch has always latest navigation. Something like the internals is not even suitable for getting started! Remember the goal of this page is to guide users getting started with the template and is a one-time thing. From the point component is removed, users should already be able to navigate through docs and find useful links like discord to ask their questions. They cannot come back to this to find other links. (later-on we can probably have a tutorial page with devtools but they are not the same)

I don't have strong opinion here But I can definitely agree with what you saying. I like to have a minimalistic approach. Example of socials can only be a clickable button and should be enough the join us is an extra addition that can be not necessary.
About the old one what I think the new one has a more elegant approach.  And in that case same comment about twitter text.
Maybe we can find a way to reduce the amount of element in the new one. I agree that having only one link for getting started will reduce potential failure if the doc endpoints change. And also adding the started part at the same level.
Having socials in this page is interesting I think. But can be more minimalistic. Also would be good to have more analytics in this page. Like a shorten url for social and docs so we know where the user is coming from and the actual usage of this page.
I am totally fine to rework this page Ping me when you come with a consensus

I believe we need to add text under each social part instead of Join us. Question is why should they click on it?
For example:

Twitter: discover the latest updates and news regarding Nuxt
GitHub: engage and contribute with the framework
Discord: ask your questions and help the community in real time

I think we need to clearly define what we want to showcase on that page before designing it :thinking:

For example:

Twitter: discover the latest updates and news regarding Nuxt
GitHub: engage and contribute with the framework
Discord: ask your questions and help the community in real-time

Please consider that users see this page one time with a starter template. I think we should reserve space for built-in futures like starting with built-in dev tools instead and keep icons minimal.

Hey what's the update on it? Should I come with an idea ? Or @R-mooon you are working on something already ?

Following on #81, thank you so much for your help and feedback @jsbaguette


OpenCL registration method not available!

when follow step 7.1 to execute "roslaunch kinect2_bridge kinect2_bridge.launch"
i got this error :
[kinect2_head_kinect2_bridge-2] restarting process
process[kinect2_head_kinect2_bridge-2]: started with pid [3236]
[DepthRegistration::New] OpenCL registration method not available!
[DepthRegistration::New] OpenCL registration method not available!
[OpenGLContext] failed to initialize glew for the current context!
i search in code iai github and found that is because libfreenect2 does not initialize glfw. dude
how i fix this problem ?

i repeate step 1 - 6 and got new error
output in termnal :
[kinect2_head_kinect2_bridge-2] restarting process
process[kinect2_head_kinect2_bridge-2]: started with pid [3134]
[DepthRegistration::New] Using OpenCL registration method!
[DepthRegistration::New] Using OpenCL registration method!
[OpenGLContext] failed to initialize glew for the current context!
i still trying to figure it out...

@motionagus,
currently open_ptrack requires a CUDA-capable graphic card if you want to use the Kinect v2 (see https://github.com/OpenPtrack/open_ptrack/wiki/Supported-Hardware).
You can use OpenCL or the CPU instead of OpenGL for the packet pipeline by modifying kinect2_bridge.cpp inside the packet iai_kinect2, but it is not tested yet.

@marketto89 : if i installed supported cuda graphics card, does test point cloud likely going to work ? i still dont know what kind of view i get when point cloud is work.
btw dude i actually dont understand  what you mean by using OpenCL or CPU instead of OpenGL for packet pipeline, btw what its gonna do ?

Yes, if you install a supported CUDA graphic card and you follow the OpenPTrack wiki (https://github.com/OpenPTrack/open_ptrack/wiki), you should not have any problem.
By the way, if you choose to test anyway the Intel HD4600,take care that this is an unsupported card and you could likely have problems. In this case, the first thing I would test is to change the row 154-165 of kinect2_bridge.cpp to be sure to invoke  packetPipeline = new OpenCLPacketPipeline(deviceId) and depthRegLowRes = DepthRegistration::New(DepthRegistration::CPU);     depthRegHighRes = DepthRegistration::New(DepthRegistration::CPU);.

@marketto89  i tried to change it but still didnt work.

maybe i should installed cuda supported vga.
btw @marketto89  or @mmunaro did you know the percentage for accurate of openptrack to counting people cause as far as i know when using blob method to determine people its always not perfect.

@motionagus

OpenCL or CPU instead of OpenGL for packet pipeline, btw what its gonna do ?

these all refer to how the Kinect 2 driver is being processed - it can be done with CPU (normal - but very intensive) or GPU (more efficient) . To use GPU one must use an SDK/Library, and that's where CUDA, OpenGL, and OpenCL come in. Each roughly do the same thing, but with different libraries.
The only supported solution is OpenGL.
If you're doing something other than what is on https://github.com/OpenPtrack/open_ptrack/wiki/Supported-Hardware
such as Intel GPU or OpenCL - we can point you in the right direction , but you're on your own.
if you want a working system, stick to the supported hardware, and follow the wiki.
If you do that, then yes, it tracks extremely well from the start.
it can indeed be tuned so there are zero false tracks, and IDs are very persistent.
as can be seen from the vimeo page. https://vimeo.com/channels/864928
So the percentage may not be 100%, it's very close, and far closer than any other system I've seen (though there is no other system quite like this one, and certainly not open sourced).
Thanks for your interest in the project!


Don't write compressor if None

According to the latest spec, when there is no compressor it must not even be written to the array metadata JSON file.

Thanks @davidbrochart, I've pulled this into master manually.


Gcc 4.9 floating point conversion issue (#871).

See #871

Hmm. Looks like MInGW doesn't know __GNUC_PREREQ...

Maybe it has another name? If i remember correctly, there's such a macro in MinGW.

__MINGW_GNUC_PREREQ :-(

Thanks, i have added separate checks for Gcc and Mingw now.

Seems this did more damage than help ...

I think this should do nicely:
#if defined(__GNUC_PREREQ)
  #if __GNUC_PREREQ(4, 9)
    #pragma GCC diagnostic ignored "-Wfloat-conversion"
  #endif
#endif

If Mingw suffers from the isnan() problem as well, we can do the full shebang in CppUTestConfig.h.

Not so fast.... there's clang, too, and it has GNUC defined, but doesn't know GNUC_MINOR__ so we arrive at this:
/* GCC 4.9.x introduces -Wfloat-conversion, which causes a warning / error
 * in its own (macro) implementation of isnan() and isinf()
 */
#if defined(__GNUC__) && defined(GNUC_MINOR__)
 #if __GNUC__ >= 5 || ( __GNUC__ == 4 && GNUC_MINOR__ > 8 )
  #pragma GCC diagnostic ignored "-Wfloat-conversion"
 #endif
#endif

via #901


Site can't find solr

I'm unable to get the drude-d7-testing project to recognize apache solr
Per  apache-solr.md I added a solr node to docker-compose.yml:
# Solr node
# Uncomment the service definition section below to start using Solr.
solr:
  hostname: solr
  image: blinkreaction/drupal-solr:3.x-stable
  environment:
    - DOMAIN_NAME=solr.drupal7.drude

Downloaded and enabled apachesolr-7.x-1.x-dev and setup a server at admin/config/search/apachesolr/settings/add with the url
    http://solr.drupal7.drude:8983/solr

Testing the connection from admin/config/search/apachesolr/settings/solr/edit
gives me the warning Your site was unable to contact the Apache Solr server.
Output of dsh ps
        Name                       Command               State        Ports
---------------------------------------------------------------------------------
druded7testing_cli_1    /opt/startup.sh gosu root  ...   Up      22/tcp, 9000/tcp
druded7testing_db_1     /entrypoint.sh mysqld            Up      3306/tcp
druded7testing_solr_1   java -jar start.jar              Up      8983/tcp
druded7testing_web_1    /opt/startup.sh apache2 -D ...   Up      443/tcp, 80/tcp

Try http://solr:8983/solr.
We have to updated the docs to account for the v2 docker-compose file format and newer docker versions.

Worked! Thanks.


IdentityServer4 and Entity Framework

Will be released one version where IdentityServer4 works together with asp.net Entity Framework?
Best regards

Here is an implementation.
https://www.nuget.org/packages/TwentyTwenty.IdentityServer4.EntityFrameworkCore/

I would like to see a example with two or more applications, where one is the Identity server and the others the clients.
In the identity server, the users and roles cames from Entity Framework tables.
The clients applications make single sign on, in identity server application, and have to respect some roles.
Thank you and best regards


Raise InvalidMoveError when block confirmed not yet

resolved #135

Codecov Report

Merging #137 into master will decrease coverage by 1.06%.
The diff coverage is 97.56%.

@@            Coverage Diff             @@
##           master     #137      +/-   ##
==========================================
- Coverage   79.12%   78.05%   -1.07%
==========================================
  Files          42       42
  Lines        2247     2288      +41
==========================================
+ Hits         1778     1786       +8
- Misses        469      502      +33

Impacted Files
Coverage Δ

tests/models_test.py
98.1% <100%> (+0.32%)
:arrow_up:

nekoyume/models.py
76.2% <94.44%> (+0.56%)
:arrow_up:

nekoyume/items/base.py
60% <0%> (-24%)
:arrow_down:

nekoyume/items/weapons.py
53.84% <0%> (-23.08%)
:arrow_down:

nekoyume/battle/simul.py
67.14% <0%> (-18.58%)
:arrow_down:

nekoyume/battle/components/bag.py
46.34% <0%> (-7.32%)
:arrow_down:

nekoyume/tables/__init__.py
93.23% <0%> (-4.52%)
:arrow_down:

...ume/battle/components/behaviors/skills/__init__.py
56.66% <0%> (-0.67%)
:arrow_down:

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 9d03902...f5bd20f. Read the comment docs.


Shorten WestDAAT URLs

We need to use a service that shortens the WestDAAT's URL for data-sharing purposes. Here is an example of a URL that was shared with us through feedback submissions. It's getting out of control how long it has become.
Useful resources to look into

https://learn.microsoft.com/en-us/shows/azure-friday/azurlshortener-an-open-source-budget-friendly-url-shortener

https://medium.com/marcus-tee-anytime/create-your-own-url-shortener-host-in-azure-almost-free-for-cloud-infrastructure-a74c9cc29720

WestDAAT long URL example
https://u25918979.ct.sendgrid.net/ls/click?upn=vvecQssSvf-2FaCxZpfrW1NzSrcL3gcPfhraL3ROKNkPWKoh-2FKKWBrzMDtSYYzhh-2BcEyrZOBZzbXjo3jZwaE45r0-2FyEWvQwvk23keaVFYLCS3wLBLnJfFellyFXGbk784sWDIcnH4NGIsttqi-2FZ-2B6TLa6KuS5PCTkYkBHu7MeZYcDxzLTl9NYdsGssacDQ4WtXKDLZa7FyUnn1Wi5iNxfj8CjmV2CICvOVXt1YvvcojnqFQhX-2BaJd8-2FTJ-2Fjd81NJ1wyeh-2FscQJDlIbLxrYq2tfISSf3tM-2BVB-2FKy7VLiZ3e-2FaaCg8IqpOonwB-2F9ZXk0jh3WgHqEX8frDb6xK3Td8M1Gs4HsDiJAghNV6SaMx60k8Mz-2BWbywr7mAlxuuFg5zbSMzBZM6aG-2FXAI4YnA0ztTJ0NB87BudSAk5sIkqThb81xuKvNASARDGsQKnj7L833qSVkG2-2B0JecEMIxwA0vpv9p1EKxHLxJzEx7OiLNgOAN-2F3pHRTUmXtnzVqMQlZSP-2BSQvyKoz_uCiIOgIgJtGs5RiWiA58yR-2FRK3CK-2B6-2BDkFmOVDa7Sn0n4C62sIGJ1hqHj-2FCse8WAjNl5L-2B-2B6xBCMIuUrZyvTbhwulG6jXBkAWQCvHmEqOV0QMWUMU7bvepN3gkOFOt8WjylJzRoAz-2BDlynscwjQ1elSwAdbO6nqXzrnl2Tg1rJ9FJmK8dj9-2FoZ-2FDcvyU1YRI8lBJpDJtgg-2F9aCakz-2BCA4U3ReRDvC7xjJMvQzrB9Yqg-3D

A couple of things on this.
First, the URL you just linked is a SendGrid URL that tracks whether the link has been clicked in the email.  The actual URL is
https://westdaat.westernstateswater.org/?state=N4Ig7gTiBcoM4BcCGCCmcYG0QBUAaIAugDQgAOA9gDYCeVAlgHapYkiNUAm9AYvVWggARFEhigqKeggCunFtADMABgB0ygBwbFpKhUYBzaXIUBaAJwB2VQCYbygGyluEVAGME9fRiXPRABQomBB9LAF8w0gBbJDJxEAAvCgoogBlUADdUKhgARjVLczsAFgdFXKLFB3Ni3SlZeRgVdRtSy0UNXMtinssHWpA9Q2NG6AtrXOKbBwdLAFZHFWLFOcj2Lnp4yU8GhWbNbV19I12Ycdt7JxAXd09vJr9kQODQtY5uAEEPeiyYBAgZKgwkA
that is about 60% less than what SendGrid uses for this example.  A quick search makes it look like the URL tracking can be turned off if necessary (https://stackoverflow.com/a/43145800/4552551).
Second, URL shorteners don't make the URL shorter despite the name.  They provide an alias for a URL.  Think of it as a "nickname" for the URL.  You can call the URL by a different name, but it will still be long.  For instance, when you go to https://aka.ms/networksetup you end up at https://support.microsoft.com/en-us/windows/get-connected-when-setting-up-your-windows-11-pc-50dca26f-40d5-4c3b-853c-e972dafb7e08.
This scenario is not a use case where URL shorteners are typically used.  URL shorteners are great when sending a URL in a medium with limited text, like Twitter or SMS messages.  However, URL shorteners also add a new dependency to your system that can have outages, reduce system availability, and degrade performance.
When you have many parameters you need to be able to link back to, URLs get long.  Even Google ends up with long URLs when you start to add conditions to your search (https://www.google.com/search?q=are+long+urls+bad&lr=lang_en&cr=countryUS&safe=active&tbs=qdr%3Ay%2Clr%3Alang_1en%2Cctr%3AcountryUS&sxsrf=APwXEddFqkBjtsbxiCM83Rk0bE1t_OcKbQ%3A1683731757526&ei=LbVbZPW5H-irqtsP4o2VkAc&ved=0ahUKEwi1hLfKhev-AhXolWoFHeJGBXIQ4dUDCBA&uact=5&oq=are+long+urls+bad&gs_lcp=Cgxnd3Mtd2l6LXNlcnAQAzIECCMQJzIFCAAQgAQyBQgAEIAEMggIABCKBRCGAzIICAAQigUQhgM6CggAEEcQ1gQQsAM6BwgjEIoFECc6CAgAEIoFEJECOhEILhCABBCxAxCDARDHARDRAzoLCAAQgAQQsQMQgwE6CwguEIAEEMcBENEDOgcIABCKBRBDOggIABCABBCxAzoICC4QgAQQsQM6CwguEIAEEMcBEK8BOg0IABCKBRCxAxCDARBDOgsIABCKBRCxAxCDAToECC4QAzoKCAAQgAQQFBCHAjoICAAQFhAeEA86BggAEBYQHkoECEEYAFDpAljlJmCpLmgBcAF4AIABjQGIAa0PkgEEMS4xNpgBAKABAcgBCMABAQ&sclient=gws-wiz-serp).  This Google URL is 90% larger than the one from WestDAAT and doesn't cause a problem for Google (and I have no idea why it is so long or what it contains).
There are some ways we can reduce the URL length a little, with some denser data structures and clever URL construction.  However, changing filters and site options will result in less flexibility and more development effort in the future.  There is a long-term maintenance cost to making such a change.
Long URLs are not a signal of a problem.  In your case, they are only a sign that you have a robust filtering system with lots of flexibility.


simplify flags

removed "install-" flag prefixes
added install/uninstall info messages

Codecov Report

Merging #28 (26c3821) into main (46a7c5d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #28   +/-   ##
=======================================
  Coverage   25.13%   25.13%
=======================================
  Files           1        1
  Lines         187      187
=======================================
  Hits           47       47
  Misses        134      134
  Partials        6        6

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 46a7c5d...26c3821. Read the comment docs.


When I type "<" in html file, it creates empty space instead of writing "<"

Issue Type
Bug
Description
When I type '<' in html file, it creates empty space instead of writing '<'
VS Code Info
VS Code version: Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:34:36.336Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz (4 x 2594)

Memory (System)
7.69GB (1.64GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

beautify
Hoo
1.3.0

(1 theme extensions excluded)

Reproduces only with extensions

Cannot reproduce the problem.
Can you reproduce this when you have the extensions disabled?
Please provide a snippet that illustrates the problem.

I can still reproduce this issue.
Issue is not reproducible if i disable my all extensions.
Following are the extensions that was enabled and the issue was getting reproduced.


Issues if the container registry (serverURL) isn't just the hostname

Hi!
Thank you for the great work of maintaining this package. :1st_place_medal:
I've been troubleshooting an issue with cosign when it comes to authenticating to the Azure Container Registry. One of the issues I've found is that somewhere along the way, the whole container image URL is passed to your helper and it causes the authentication to fail.
Reference for the method: https://github.com/chrismellard/docker-credential-acr-env/blob/fe33c00cee21eacc9fc67b6492b2c0cbe08b8bbe/pkg/credhelper/helper.go#L67
If we look at the same Elastic Container Registry (AWS) helper, we can clearly see them extracting information before passing it to their other functions: https://github.com/awslabs/amazon-ecr-credential-helper/blob/69c85dc22db6511932bbf119e1a0cc5c90c69a7f/ecr-login/ecr.go#L46
I'll create a PR for you to review.
Reference for the cosign issue: https://github.com/sigstore/cosign/issues/1350

Hi! 👋
I added that code in #2 and I think I see the bug. I'll send a PR now.

@imjasonh hi! 😊
I was actually experiencing the issue before using your patch. Or at least I think so. 🤔

@imjasonh please take a look at the following before: https://github.com/chrismellard/docker-credential-acr-env/pull/4

@imjasonh hi! 😊
I was actually experiencing the issue before using your patch. Or at least I think so. 🤔

Yep, I thought I was looking for a bug in Get when it looks like it's actually just the refresh token flow when repos are included. Completely missed your PR, which is much better 😆

@imjasonh Do you think we should still add this even tough we fixed it in go-containerregistry?

I'll leave that up to @chrismellard -- the normal way this code is called is with just the hostname and no path component, it was (seemingly) only due to a bug in that library's usage that it was being called in any other way.
In the spirit of Postel's Law it might make sense to be more flexible in what this accepts, but I don't think we need it anymore, since we're doing the right thing now.

Great! It's up to you @chrismellard :+1:


evaluation on SQA very slow

when I follow instructions run eval on SQA, the inference is very slow, however I find that web broswer demo is very fast.

I eval on 8 gpus and it cost nearly one hour to inference on ~5K

How can I use multiple cards for reasoning? @JulioZhao97

Hi @mary-0830
You can use our scripts for write yours for multiple GPU (batch inference): https://github.com/haotian-liu/LLaVA#evaluation-1

Hi @mary-0830 You can use our scripts for write yours for multiple GPU (batch inference): https://github.com/haotian-liu/LLaVA#evaluation-1

ths!!


Update the security policy to prevent some back and forth with the community

LGTM, perhaps we should also instruct folks to stop sending automated security scans as CVEs?

@jonkoops updated


Update Django and Python

@Eorhim python3.7 does not exist for ubuntu 14 I assume, so our CI fails


added while_inside_goto test

#66

@rultor merge

@rultor merge

@mikhaillipanin OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@mikhaillipanin Oops, I failed. You can see the full log here (spent 2min)
+ sensitive=()
+ rm -rf .gnupg
+ cd repo
+ git remote add fork git@github.com:MikhailLipanin/dejump.git
+ git remote update
Fetching origin
Fetching fork
From github.com:MikhailLipanin/dejump
 * [new branch]      95             -> fork/95
 * [new branch]      add_while_test -> fork/add_while_test
 * [new branch]      main           -> fork/main
 * [new branch]      new_test       -> fork/new_test
+ args=
+ '[' default == default ']'
+ args=' --ff'
+ '[' default == no ']'
+ '[' default == only ']'
+ export BRANCH=__rultor
+ BRANCH=__rultor
++ git show-branch __rultor
++ wc -l
+ '[' 0 -gt 0 ']'
+ git status
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
+ git checkout -B __rultor fork/new_test
Switched to a new branch '__rultor'
Branch '__rultor' set up to track remote branch 'new_test' from 'fork'.
+ git checkout -B master origin/master
Switched to and reset branch 'master'
Branch 'master' set up to track remote branch 'master' from 'origin'.
Your branch is up to date with 'origin/master'.
+ '[' false == true ']'
+ '[' false == true ']'
+ git merge --ff __rultor
Updating f13d802..9782960
Fast-forward
 src/test/eo/org/eolang/dejump/while_inside_goto.eo | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 src/test/eo/org/eolang/dejump/while_inside_goto.eo
+ docker_when_possible
+ true
++ uptime
++ sed 's/ /\n/g'
++ tail -n 1
+ load=0.12
++ echo 0.12 '>' 30
++ bc
+ '[' 0 -eq 1 ']'
+ echo 'load average is 0.12, low enough to run a new Docker container'
load average is 0.12, low enough to run a new Docker container
+ break
+ cd ..
+ '[' -n '' ']'
+ use_image=yegor256/rultor-image:1.9.1
+ docker pull yegor256/rultor-image:1.9.1
Error response from daemon: Head "https://registry-1.docker.io/v2/yegor256/rultor-image/manifests/1.9.1": received unexpected HTTP status: 503 Service Unavailable
'cid' file is absent, most probably the Docker container wasn't started correctly

@rultor merge

@rultor merge

@mikhaillipanin OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@mikhaillipanin Done! FYI, the full log is here (took me 3min)


React native 0.60+

Hi. There is a new feature in react-native 0.60+ which is called autolinking. And CocoaPods is used by Default. So Autolinking relies on .podspec file. I tried to fork your repo and add a .podspec file but I've failed(. When i try to link manually - i catch this error

@max-zu I've opened a PR to address this, can be found here: https://github.com/lyubo/react-native-sodium/pull/24
This podspec works well for my RN > 0.60 project


chore: fix NewMessageT order

LGTM. Let's update the corresponding images when making changes to the UDFs.

Also please update the function call in numaflow as well.


Compact Representation Format for PK Tokens

This issue proposes a Compact representation for PK Tokens. The goals of such a format are:

Must avoid multiple base64 encodes to result minimal size, that is a compact representation,
Must handle including JKT of OP public key, if one exists
Must handle refreshed ID Tokens
Must not include unsigned values

Proposed Format
Our compact representation format for PK Token:
Base64(payload)+":"+Base64(protected1)+":"+Base64(sig1)+":"+Base64(protected2)+":"+Base6464(sig2)
If we wish to include a refreshed ID Token, we add it to the back using the JWT compact representation: Base64(refreshed-protected)+"."+Base64(refreshed-payload)+"."+Base64(refreshed-sig) and get:
Base64(payload)+":"+Base64(protected1)+":"+Base64(sig1)+":"+Base64(protected2)+":"+Base6464(sig2)+"."+Base64(refreshed-protected)+"."+Base64(refreshed-payload)+"."+Base64(refreshed-sig)`
Parsing
This compact representation is intended to be easy to parse.
compact_PKT, compact_RIDT.protected, compact_RIDT.payload, compact_RIDT.sig=Split(".", compact_PKT)

parts=Split(":", compact_PKT)
compact_PKT.payload=parts[0]
compact_PKT.protected1=parts[1]
compact_PKT.sig1=parts[2]
compact_PKT.protected2=parts[3]
compact_PKT.sig2=parts[4]
...
compact_PKT.protected2=parts[n]
compact_PKT.sig2=parts[n+1]

The JKT field
Currently we include the jkt (JSON Key Thumbprint) field as a public header as discussed in How do we deal with missing/non-unique kid on JWKS endpoint?. Since public headers are not signed, it will not be included in the compact representation. To include it we add a new rule to the CIC construction: CIC claims that start with underscores (_) are not included in the CIC commitment. Thus, if a user wants to include the JKT in the Compact representation, they can do so by putting it the CIC protected header as "_jkt" and then sign it.
  {"protected": {"upk": alice-pubkey, "alg": "EC256", "rz": crypto.Rand(), "typ": "CIC", "_jkt": "0ZcOCORZNYy-DWpqq30jZyJGHTN0d2HglBV3uiguA4I"},
  "signature": <SIGN(alice-signkey, (payload, signatures[1].protected))>
  },

After talking this over with @mrjoelkamp it seems like a potentially very nice solution for JTKs in compact representation is to put it in the GQ signed OP protected header.
When replacing the RSA signature with a GQ Signature, we create a new protected header that contains the original RSA protected header in kid. We could easily just add the jtk to the new GQ protected header.
The downside to this approach is that it only works for GQ signed PK Tokens. Maybe that is ok.


cosign download attestation cannot filter by attestation predicate type

Description
Given a test image:
$ IMAGE='quay.io/lucarval/festoji@sha256:61ac53fe9316734ed8a8bc6418b2c371730a2c122b5df1d7f76b960d381f5457'

I can download all of its attestations:
$ cosign download attestation $IMAGE | jq '.payload | @base64d | fromjson | .predicateType'
"https://slsa.dev/provenance/v0.2"
"https://spdx.dev/Document"

However, I cannot use the --predicate-type parameter to select the SLSA provenance attestation:
$ cosign download attestation $IMAGE --predicate-type 'https://slsa.dev/provenance/v0.2'
Error: no attestations with predicate type 'https://slsa.dev/provenance/v0.2' found
main.go:74: error during command execution: no attestations with predicate type 'https://slsa.dev/provenance/v0.2' found

However, it does work for the SBOM attestation:
$ cosign download attestation $IMAGE --predicate-type 'https://spdx.dev/Document'
{"payloadType":"application/vnd.in-toto+json","payload":"...

Version
🐚 cosign version
  ______   ______        _______. __    _______ .__   __.
 /      | /  __  \      /       ||  |  /  _____||  \ |  |
|  ,----'|  |  |  |    |   (----`|  | |  |  __  |   \|  |
|  |     |  |  |  |     \   \    |  | |  | |_ | |  . `  |
|  `----.|  `--'  | .----)   |   |  | |  |__| | |  |\   |
 \______| \______/  |_______/    |__|  \______| |__| \__|
cosign: A tool for Container Signing, Verification and Storage in an OCI registry.

GitVersion:    v2.0.2
GitCommit:     871448050b924a7946ebe47678f23aae09ef432d
GitTreeState:  clean
BuildDate:     2023-04-24T17:31:42Z
GoVersion:     go1.20.3
Compiler:      gc
Platform:      linux/amd64

I can also reproduce the issue on the current HEAD of main (83c08ce4f35116da7c74350a67d5740ca5e28ca5).

It looks like the cosign download attestation command requires the predicateType annotation when filtering: https://github.com/sigstore/cosign/blob/83c08ce4f35116da7c74350a67d5740ca5e28ca5/pkg/cosign/fetch.go#L153-L163
Sure enough, the SLSA Provenance attestation doesn't have that annotation, but the SBOM does.
There's disparity in how the download attestation and the verify-attestation commands work. I can filter by predicate type on the second:
cosign verify-attestation $IMAGE --certificate-identity-regexp '.*'  --certificate-oidc-issuer-regexp '.*' --type 'https://slsa.dev/provenance/v0.2'

Verification for quay.io/lucarval/festoji@sha256:61ac53fe9316734ed8a8bc6418b2c371730a2c122b5df1d7f76b960d381f5457 --
The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - Existence of the claims in the transparency log was verified offline
  - The code-signing certificate was verified using trusted certificate authority certificates
Certificate subject<EMAIL_ADDRESS>Certificate issuer URL: https://token.actions.githubusercontent.com
GitHub Workflow Trigger: push
GitHub Workflow SHA: d9f2616186b454700a4c196e696b9a60fdcecfdb
GitHub Workflow Name: Package
GitHub Workflow Repository: lcarva/festoji
GitHub Workflow Ref: refs/heads/master
{"payloadType":"application/vnd.in-toto+json","payload":"

That's the because the verify-attestation command parses each attestation and does a comparison of the predicate type based on the payload data:
https://github.com/sigstore/cosign/blob/83c08ce4f35116da7c74350a67d5740ca5e28ca5/pkg/policy/attestation.go#L84-L87

The problem seems to be that older cosign versions do not add the predicateType annotation. In fact, it was added simultaneously with support for filtering by predicate type: https://github.com/sigstore/cosign/commit/dd747eeade444d42a5c55c35adf5c17831d60c6c

That sounds right to me—it does the right thing in more circumstances (including better backwards compat).
CC @chaospuppy would love your thoughts here!

@chaospuppy, thanks for the prompt reply! See inline comments below.

Doing this meant that tools outside of the cosign ecosystem could find and retrieve the desired attestation blob using more-readily available manifest/manifest-layer metadata

I'd be overly cautious of using a field that is not part of the spec.

You wouldn't need to perform the more resource-hungry processes of decoding each payload before inspecting it

Good point. I do think we should favor correctness over performance. IMO the performance hit here is negligible.

I do think it's confusing to have started adding the annotations at the same time they became usable, but that's why the default behavior matches what it was previously, where all the attestations are returned if a --predicateType isn't specified.

The issue is that the predicateType annotation is not part of any standard. If it were, then there would've been no issue with adding support for reading and writing at the same time.

Maybe it would be best to update the fallback behavior if a --predcateType is specified, but no matching annotations are found, to use the verify-attestation method instead of failing?

I think this is an improvement over the current approach. However, I take issue in it being different than what verify-attestation does. As a user, it is very confusing when those commands don't behave the same way.
I made a PR which makes the logic the same for both commands: https://github.com/sigstore/cosign/pull/3031
Happy to hear what you think!

Ultimately I'm good with the PR being made because the annotations will still be getting created, but there's probably some followup work on my end to get the predicateType (or more likely something like dev.sigstore.cosign/predicatetype) into the layer so it's a bit more standardized.  When that happens, perhaps this short cut (no payload processing up front) could be re-added in both verify-attestation and download attestation?  Thoughts @znewman01 ?

At the risk of complicating things even further, how does this play with OCI 1.1 reference types which support a filter by artifactType? Is the artifactType always going to be just application/vnd.dsse.envelope.v1+json (in which case this is moot) or would we ever encode the predicate type into the artifactType somehow?
CC @sudo-bmitch

Overall I defer to you all. My priorities are consistency between the different commands and correctness (no surprise missing data), and performance is a distant third. So I think I'd be okay with either:

Fallback workflow: use the annotation if it exists, and if it doesn't fall back to parsing the JSON blob.
Just parse the JSON.

IIUC #3031 does (2).
Please let me know if I'm misunderstanding anything here, the OCI side of Cosign is not my strength :)

I'm not too familiar with artifactType, but it looks like, if anything, this would be set to a type that indicates that the artifact is an in-toto statement. The predicate type is one level deeper.

Fallback workflow: use the annotation if it exists, and if it doesn't fall back to parsing the JSON blob.

If we do this in download attestation, we should probably also do it in verify-attestations to provide consistency. I can think of a couple of use cases where even with a fallback option, the filtering would be different.
I think we should go with option 2, which is what the PR does, at least for now. There's a longer term feature request to push the predicate type annotation into the in-toto standard(?) to facilitate querying. Having cosign continuing adding those annotation makes sense to me and brings us closer to this goal.

For an artifact, you do not want to use "application/vnd.oci.image.config.v1+json" for the config. That's a sign that this is a container image (though runtimes will throw errors when they see the layer media type). Instead you either need a dedicated config blob with your own type and content, or if you have no separate config, you would use the artifactType field. We are finishing up what the config descriptor would contain in https://github.com/opencontainers/image-spec/pull/1068, but most likely an artifact that is just a application/vnd.dsse.envelope.v1+json blob would have something like the following manifest:
{
  "schemaVersion": 2,
  "mediaType": "application/vnd.oci.image.manifest.v1+json",
  "artifactType": "application/vnd.dsse.envelope.v1+json",
  "config": {
    "mediaType": "application/vnd.oci.empty.v1+json",
    "digest": "sha256:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a",
    "size": 2
  },
  "layers": [
    {
      "mediaType": "application/vnd.dsse.envelope.v1+json",
      "size": 8216,
      "digest": "sha256:90e4d184b4a6635ec6f3b88e244de0b7fe0a078569bbec710ea9109db29d8712",
      "annotations": {
        "dev.cosignproject.cosign/signature": "...",
        "dev.sigstore.cosign/bundle": "...",
        "dev.sigstore.cosign/certificate": "....",
        "dev.sigstore.cosign/chain": "....",
        "predicateType": "http://example.mytype"
      }
    }
  ]
}

You'll likely want to feature gate this behind the oci-1-1 options in cosign since we haven't GA'd this yet. The one registry that I know you'll want to work with is GitLab who has an allow list on their config mediaType and may do the same for the artifactType.

So sounds like you're on the money @lcarva, we will still need to set the annotation if we wish to identify which layer contains the desired predicate type, even after reference types are introduced.

Assuming you only have a single layer, you would want to define any annotations useful for filtering on the manifest itself, rather than the layer. Annotations on the manifest are pulled up in the referrers response, allowing you to pick the dsse envelope artifact from a list of artifacts all created for the same image.
This is a bit different from the current cosign design where there's one attestation manifest with multiple layers. The goal of the OCI design is to make it easier to add and remove entries, especially when the registry is managing the referrers response.


Logging and exception cleanup

Log levels should be reduced to debug for info messages, and the stream close() methods should nt throw exceptions.

Fixed in v1.0.1


Support new dynamically linked binary apt and yum repos

Announcement here: https://blog.docker.com/2015/07/new-apt-and-yum-repos/

Linking to #394

@st-isidore-de-seville / @someara Any updates on this issue?
I'm hitting a snag with a production app and could really use that dynamically linked docker binary. I'd be willing to help out with a PR but I don't want to duplicate work if you guys have something in motion. :smiley:

hey @JamesAwesome, I was working on creating cookbooks that would link to their repositories and it should be done by tonight.  That being said, once I turn that over to @someara, I guess we will have to evaluate how that fits into his overall cookbook.  I imagine that there is probably some refactoring that has to occur but I do not want to speak for him.

Thank you for the update :+1:

@JamesAwesome: I was having trouble with testing and travis-ci and did not get as far as I planned to.  the yum-docker cookbook: https://github.com/st-isidore-de-seville/cookbook-yum-docker/tree/initial which takes care of the yum docker repos is almost finished and I am trying to have the apt docker repo cookbook finished shortly thereafter.  my apologies for the delay.

No need to apologize! Thank you for keeping me posted though, I just wanted to make sure somebody was hacking at it, if not I would have volunteered to lend a hand. :smile:

@JamesAwesome, here is the first one for the docker yum repository https://supermarket.chef.io/cookbooks/yum-docker

@JamesAwesome, here is the repo for the docker apt repository: https://github.com/st-isidore-de-seville/cookbook-apt-docker.  I just have to promote it to Supermarket this afternoon and I guess @someara will take it from there.

https://supermarket.chef.io/cookbooks/apt-docker

:+1: awesome, thank you @st-isidore-de-seville !

Excellent. I'll take a look at these later this week!
-s
On Tue, Sep 8, 2015 at 4:08 PM, James Awesome Morelli <
<EMAIL_ADDRESS>wrote:

[image: :+1:] awesome, thank you @st-isidore-de-seville
https://github.com/st-isidore-de-seville !
—
Reply to this email directly or view it on GitHub
https://github.com/bflad/chef-docker/issues/345#issuecomment-138570362.

Just took a look at these cookbooks. Great job!
I'll start utilizing these in the next major release. Thanks!
-s

Thanks @someara.  I greatly appreciate it!

Hi !
It would be really nice to use official debian packages provided by Docker Inc.
This should allow reuse of their provided SysvInit scripts (/etc/init.d and /etc/default/docker) which will simply this cookbook !
Regards,

Linking to #520 where @chasebolt suggests using the get.docker.com script

:+1:

Making moves on this...
@st-isidore-de-seville heads up, PRs incoming for apt-docker and yum-docker

Thanks @someara!  Taking a look at this currently.

Hey @someara.  Since both PRs were similar in nature, I attached some questions to one of them.  Mostly it is just for learning on my part since I feel I am still new to this community and eco-system.  I am also resolving some the failed Travis-CI builds and once I can resolve them, I will merge them and promote to the Supermarket.  Thanks again!

Hey @someara, I was able to fix my build issues and these have been promoted to the Supermarket.

Excellent. Thanks!
-s
On Sat, Oct 24, 2015 at 1:00 PM, St. Isidore de Seville <
<EMAIL_ADDRESS>wrote:

Hey @someara https://github.com/someara, I was able to fix my build
issues and these have been promoted to the Supermarket.
—
Reply to this email directly or view it on GitHub
https://github.com/someara/chef-docker/issues/345#issuecomment-150833912
.

@someara, I see this has been added but a quick question ... The https://get.docker.com/ appears to do more than just install the package.  It does some other configuration on the system.  See example below:
# aufs is preferred over devicemapper; try to ensure the driver is available.
			if ! grep -q aufs /proc/filesystems && ! $sh_c 'modprobe aufs'; then
				if uname -r | grep -q -- '-generic' && dpkg -l 'linux-image-*-generic' | grep -q '^ii' 2>/dev/null; then
					kern_extras="linux-image-extra-$(uname -r) linux-image-extra-virtual"

					apt_get_update
					( set -x; $sh_c 'sleep 3; apt-get install -y -q '"$kern_extras" ) || true

					if ! grep -q aufs /proc/filesystems && ! $sh_c 'modprobe aufs'; then
						echo >&2 'Warning: tried to install '"$kern_extras"' (for AUFS)'
						echo >&2 ' but we still have no AUFS.  Docker may not work. Proceeding anyways!'
						( set -x; sleep 10 )
					fi
				else
					echo >&2 'Warning: current kernel is not supported by the linux-image-extra-virtual'
					echo >&2 ' package.  We have no AUFS support.  Consider installing the packages'
					echo >&2 ' linux-image-virtual kernel and linux-image-extra-virtual for AUFS support.'
					( set -x; sleep 10 )
				fi
			fi

I am wondering if this logic should also be replicated in this cookbook.  I can help out if needed by just wanted to get your thoughts?

Nope. Cgroups and storage drivers are out of scope.
They're a loosely coupled dep and should be set up with other cookbooks if needed. Modern Linux comes with this stuff enabled out of the box.

That being said, I'm very happy to close this issue. =)
2.2.0 now uses the docker_installation_script resource by default, and has docker_installation_package available.
-s

Thanks again @someara for all of your hard work on this!  Please let me know if I can help out in the future!


Need to handle case of auto closing after end date

It looks like we are already handling the case of auto close dates being after end dates, both in data.can_trade and when ordering. So this (the roll finder) is the only other spot I know of that needs this change.

Coverage decreased (-0.01%) to 87.13% when pulling 90db2f7cd24fbff423cc76854d2308748f6b1c9d on yet-more-data-troubles into 03782fdfd3e49af0407b15e796adb89268997dd1 on master.

Coverage increased (+0.4%) to 87.493% when pulling 92c9932a2719e1e6244c0bb8f2304e11ee72a29f on yet-more-data-troubles into 03782fdfd3e49af0407b15e796adb89268997dd1 on master.


create Twitter module

Send automatic tweets when talks are approved/assigned to events.

tweet speakers talk titles in the run up to the event

thank speakers after event with link to slides if exist

i'm gonna work with this

i've implemented the send tweet and also added a formatter. Maybe i should leave as is,  when we really know what wil be sended to this module, do the final work in the formatter. Meanwhile I could work in other stuff

:+1:

@h02e56 can you add a list to the readme for integrations and link to your repo? ty

i ve done this changes.(maybe something missing)
Should I go to gitevents branch and make a pull?
I have to work on data comming from core to give it format

@h02e56 please add the link to the repo as @iancrowther suggested.
Thanks

I had formatted  readme incorrectly. done

im a bit puzzled? did you add a link to the readme?

lol, true, fixed
later i will comment some doubts about what i will receive

About twitter i'm formatting the event as for example:
"New @bcnjs talk! 01/21/2015 @testUser2 Development environments using fig... meetup.com "
I really don't know if i exeed the max chars it will send 2 tweets, i gess so , but i like the idea to just send one x talk or job. I'm having some problems with description formatting..
Some thoughts:
Should we automate some type or remember tweet until the date of event?
About say thanks to the speaker and link to the slides. What in github will trigger it?(new issue?)
What twitter module will receive?
I decided to start with this module without seeing that was fase 3, maybe i should had tried another one...my mistake..if u think taht maybe we should wait just tell me
Cheeers , "bona nit i tapat". :)

only send one tweet
'New @bcnjs talk!' this is redundant as its posted to the @bcnjs twitter account.  there's a few chars back.  can you make the description a link to the talk (issue or website)? that way it can be elipsed.

remember tweet until the date of event? - yes, maybe add a label to say tweeted so it only posts once, ever

"About say thanks to the speaker and link to the slides"
can we use event date + 1? can you access event date?  i wish the milestones api would arrive!

I think this is a key feature so should continue :-) doing great!

👍

Hi
I liked the idea of : "make the description a link to the talk (issue or website)"
I have been trying but twitter api gives me some problems or I'm missing something.
As far i understand  we should use twitter entities:
I have used "'twitter-text" to create them and also I ve used bitly api to get some t.co "twitter style " urls becouse I  thought that twitter entities require them.
I will ask you if someone has some clue about it
Thank you!

I don't remember exactly, because I used twitter api with node with twit, but I don't remember that I had issues with URLs, nonetheless I was more getting tweets than sending.
What happens when you send a tweet with an URL?

If we send a url it will creat a t.co style url
As Ian suggested could be a good idea to write the event description text and used as a link to the event page(meetup or whatever). To achieve this, looking at documentation looks like we should use "twitter entities" . As far i understand this entities could be used to get info from tweets an also to send messages .
To send messages i'm using "node-twitter" that looks very similar than yours(twit)
I'm also using 'twitter-text' to generate the entities. Tying this it didn't work and i thought that maybe we should send a already created shorten url(t.co style), so I create them, but anyway it doesn't work as expected.
Maybe i'm complicating myself, and the api is not very handy, and maybe we should take another option. if you want to take look:
https://github.com/h02e56/gitevents-twitter/blob/dev/formatter.js
what right now are sending is something like this: New talk: flE8Jhttp://bit.ly/1Dq9pmg
If we send a standard url we will get a t.co shorten url if url is too long. Maybe we should go this way and later improved
Gràcies Ivan

I don't get you, what are the benefits to use the entities? You said that is working without them, then I think that for the first release would be fine and after, and we'll improve for the next ones. For my point of view is more important to have the actions which work and after add the fancy things in future iterations.
I will try to pull your code in the weekend and run it and try to see the issues to have a better understanding.
Gràcies you for the collaboration.

Yep,
As far I understood to make a tweet like this: "new talk: mvc in depth" where text "mvc in depth" is a link to the event page we should use entities, but maybe i'm wrong. Anyway I agree with you about make module work and after add some fancy stuff.
I ve pushed a basic setup for tweet jobs and talks in my branch master
Tweet results on https://twitter.com/patstest. There are random chars to avoid that twitter consider it repeated
Is missed the greetings to the speaker

cool, thanks.

@PatrickHeneise pls add a reason for closing


[WFLY-15350] Moving Xerces & Woodstox from WildFly Core to WildFly

https://issues.redhat.com/browse/WFLY-15350
This is the initial step for eliminating JAXP hack from JBoss modules library. Once merged it will be followed with
https://issues.redhat.com/browse/WFCORE-5595 and https://issues.redhat.com/browse/WFCORE-5596

@bstansberry please review

@ropalka This seems like a WF 26 thing as it will get no bake before the 25 release due out in the next several days.

Could we get it into upstream @bstansberry ? I'd send the JBoss Modules upgrade PR against WildFly Core then to start baking JAXP changes ASAP.


[docs] Remove HighlightedCode max-width

This messes up a bit the copy button positioning: https://app.argos-ci.com/mui/material-ui/builds/31842/107814670
Not sure why it's there. Removing to see if I can find something breaking. I can't find an instance of this component where this CSS can have an impact 🤔

This was needed to fix mobile overflow. I think to check that the initial cases are not broken.

This was needed to fix mobile overflow. I think to check that the initial cases are not broken.

Do you remember which use-case this was fixing? I've been looking around at a bunch of code blocks and I can't figure out what this is trying to achieve. Seems to have initially been added in https://github.com/mui/material-ui/pull/27488.
Opening a separate ticket for some other issues I noticed.

Origin seems to be #20108

What about doing the same modification to the MarkdownElement.tsx file?

At least in screenshots that seems to fix a few more things: https://app.argos-ci.com/mui/material-ui/builds/32870/113602375
Can't find any regressions on pages that use it


Google Play Services - New Structure (rev. 30)

As it's discussed in this topic at StackOverflow it seems that google-play-services library has been substantially modified. As we've been able to test, this new changes definitely broke the extension and the only workaround for the problem is to still use old revisions (rev. 29 and older), due the impossibility of access to google_play_services/libproject.
Further updates for this extension may require to implement some big changes to access the classes and methods packed in different aar files. Is there any other possible workaround or should we stay with older revisions until future updates of this library?

Hi, If it's true that google refactored google_play_services library, then extension-googleplayservices-lib will require some work.
Meanwhile, take a look here: https://github.com/SempaiGames/extension-googleplayservices-lib/issues/3
I don't want to do anything on the extension until google officially updates it's documentation (since as today, google official documentation still says you shoud use the library inside /extras/google/google_play_services/libproject/google-play-services_lib/, so there's a small chance that they'll fix this on next release).


distro: add support for Flatcar Linux

make systemd unit path configurable as
Flatcar Linux /lib/systemd/system is read-only.

make ansible_python_interpreter configurable depending
on control host and target host. For instance,
it can be /usr/bin/python on the host and on the target
it can be /usr/home/core/bin/python.

@bbaassssiiee WDYT?

ansible_python_interpreter can best be set in the inventory.
I see too many defines of control_host_ansible_python_interpreter

@bbaassssiiee  control_host_ansible_python_interpreter is set because when host is e.g. MacOS the control host has path /usr/bin/python and the target host has, in my case, /home/core/bin/python and I have no way of defining a symbolic link to /usr/bin/python on Flatcar Linux.

@bbaassssiiee I think I can solve it as you suggest pr. host. I will test and update the PR 👍

@bbaassssiiee I have updated the PR as you suggested! It works fine with overriding inventory :)

@bbaassssiiee Is there anything else I can do in order to get this merged? :)

I had to lookup Flatcar Linux, it is supposed to run containers. Why not run consul in a container on it?

Why not run consul in a container on it?

Mostly because I can piggy-back on the conventions in this role and to avoid running consul itself in a container as it is not recommended by hashicorp.

Please fix vars/Flatcar.yml to pass yamllint in the GitHub checks.
Should be fixed now.

Bonus: add a Flatcar scenario to molecule
I tried to see how the other scenarios are done, but could not find a suitable image for it.

@bbaassssiiee I think it should be ok now.

@bbaassssiiee I have added a list of supported *nix distributions in order to avoid lint error with max characters

Nice!

:+1:


ERR: unexpected packet: 4 when receiving RTMP stream

When I push an RTMP Stream generated by a panasonic P2HD camera, RTSPSS closes the connection with the error "ERR: unexpected packet: 4".
I can receive the stream with an ffmpeg acting as a listener without a problem.
Checking the generated stream, it seems like some extra metadata is generated, and that can't be parsed by RTSPSS.
If i show packets with ffprobe, I can see the extra metadata that is probably causing the issue.
Attached are a pcap capture of the stream, and the ffprobe packet output (show_packets)
probe.log
rtmp_panasonic.tar.gz

Thanks for providing data needed to replicate the issue, this is fixed in main and will be added to the next release.

added in v0.17.4


[SPARK-38761][SQL] DS V2 supports push down misc non-aggregate functions

What changes were proposed in this pull request?
Currently, Spark have some misc non-aggregate functions of ANSI standard. Please refer https://github.com/apache/spark/blob/2f8613f22c0750c00cf1dcfb2f31c431d8dc1be7/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/FunctionRegistry.scala#L362.
These functions show below:
abs,
coalesce,
nullif,
CASE WHEN
DS V2 should supports push down these misc non-aggregate functions.
Because DS V2 already support push down CASE WHEN, so this PR no need do the job again.
Because nullif extends RuntimeReplaceable, so this PR no need do the job too.
Why are the changes needed?
DS V2 supports push down misc non-aggregate functions
Does this PR introduce any user-facing change?
'No'.
New feature.
How was this patch tested?
New tests.

ping @huaxingao cc @cloud-fan

I have a general question: what are the criteria of the functions that can be pushed down to data source?

I have a general question: what are the criteria of the functions that can be pushed down to data source?

According to discussion offline, we plan to supports the ANSI functions here.

thanks, merging to master/3.3! (it's part of the new DS v2 pushdown framework we will release it 3.3)

@huaxingao @cloud-fan Thank you!

For the recent changes in DS v2 pushdown framework, do we need to add documentation? We currently have doc for pushDownAggregate and pushDownLimit in sql-data-source-jdbc. I guess we probably want to add more doc somewhere to reflect the new changes?

For the recent changes in DS v2 pushdown framework, do we need to add documentation? We currently have doc for pushDownAggregate and pushDownLimit in sql-data-source-jdbc. I guess we probably want to add more doc somewhere to reflect the new changes?

Thank you for the reminder. I will create a PR for this.


[Bug]: Button glitch, testmode v3

What happened?
When using the testing mode in v3 and you leave it on. Refresh the page, the button state is back to the 'turn on' text while the test mode is still running.
Version
v3 beta
Distribution
CLI
OS
Linux
What browsers are you seeing the problem on?
No response
If applicable, What Listener Clients are You Using?
No response
TallyArbiter configuration
No response
Relevant log output
No response
Error stacktrace (if applicable)
No response

I am working on this right now.

#263 addresses this


Add skeleton /etc/sysconfig/docker-storage-setup

We want to encourage the use of LVM to manage docker's storage.  Our documentation instructs users to copy over /usr/lib/docker-storage-setup/docker-storage-setup to /etc/sysconfig/docker-storage-setup in order to customize defaults.
RHEL users are accustomed to looking in /etc/sysconfig to customize services, docker is no exception:
# rpm -qc docker
/etc/sysconfig/docker
/etc/sysconfig/docker-network
/etc/sysconfig/docker-storage

The lack of any /etc/sysconfig/docker-storage-setup in our package leads to some confusion about why that file does not exist.
This PR is to create a placeholder file at /etc/sysconfig/docker-storage-setup that instructs users where to find documentation on how to use docker-storage-setup, and brings docker-storage-setup in-line with the rest of the docker package's config files:

@jeremyeder
Will above patch do?

I think I will need a directive in spec file to not overwrite /etc/sysconfig/docker-storage-setup over upgrade. Instead save it in .rpmsave. I forget to remember what was that directive.

Patch merged. Closing issue.


Need Provider for Yii app

For use this implementation CSRF in yii app need provider for make CsrfToken::initialize() as here.
Suggestion:

Rewrite SessionCsrfTokenStorage.php to NativeSessionCsrfTokenStorage with use $_SESSION.

Create new package yiisoft/yii-csrf with:

Config providers.php.
Provider for initialize CsrfToken.
Implementation CsrfTokenStorageInterface with use yii sessions.

Close #3


redirect specific smartcard readers

Rebased pull-request #3416 : redirect specific smartcard readers.
Until now, /smartcard: had the behaviour to redirect every connected readers. It didn't matter what you used after the parameter /smartcard:xxxx:yyyy.
With this patch you can:
use /smartcard: "as is" (without argument) to continue to redirect every readers
use /smartcard:"Reader name" (you have to repeat that for every reader you want to redirect)
The reader name is exactly the one returned by libpcsclite, e.g.
root@host:# opensc-tool -l
Detected readers (pcsc)

Nr. Card Features Name
0 Yes Xiring Leo V2<PHONE_NUMBER>5036) 00 00
1 Yes Xiring Leo V2<PHONE_NUMBER>4712) 01 00

@freerdp-bot test

@freerdp-bot test

@akallabeth what's wrong with Windows builds ?

@freerdp-bot looks like you could re-test for windows...

@akallabeth what about the merge ?

@dodo040 wanted to test the stuff with hardware first, but failed to allocate time

@freerdp-bot test

@dodo040 wanted to test the stuff with hardware first, but failed to allocate time

@akallabeth Have you managed to allocate time for this PR ?

@dodo040 Yes, did some tests finally.
Following two things I've notices:

smartcard_init releases all device contexts, looks wrong (and prevents any successful tests on my side)
When connecting without a reader name I get errors when trying to connect with gemalto PCSC Bridge

Oh, and could you please rebase instead of the merge you did? Would remove the additional merge entries in the git log.

@freerdp-bot test


feat: add support for command [JSON.ARRLEN]

hello:
this pr is link  #484
add json.arrlen command. refer to redis json.arrlen
add unit tests in eval_test.go
because JSON.ARRLEN never change the json value, so I think there is no need to add integration test in tests/json_test.go
the json.arrlen in redis behavior as below:
`
<IP_ADDRESS>:6379> JSON.SET user $ '{"age":13,"high":1.60,"pet":null,"language":["python","golang"],"flag":false,"partner":{"name":"tom","language":["rust"]}}'
OK
<IP_ADDRESS>:6379> JSON.ARRLEN user
(error) ERR Path '.' does not exist or not an array
<IP_ADDRESS>:6379> JSON.ARRLEN user $
1) (nil)
<IP_ADDRESS>:6379> JSON.ARRLEN user $.*
1) (nil)
2) (nil)
3) (nil)
4) (integer) 2
5) (nil)
6) (nil)
<IP_ADDRESS>:6379> JSON.ARRLEN user $..language
1) (integer) 2
2) (integer) 1
<IP_ADDRESS>:6379> JSON.ARRLEN user
(error) ERR Path '.' does not exist or not an array

`
in dice, keep consistent

@JyotinderSingh
hello. in dice test workflow. I find that TestExecuteQueryWithIncompatibleTypes/NullValue sometimes it result failed,as this pr run test failed.
I test in my local env, there is one failed in fivetimes, please have a check. thanks.

@JyotinderSingh
hello. in dice test workflow. I find that TestExecuteQueryWithIncompatibleTypes/NullValue sometimes it result failed,as this pr run test failed.
I test in my local env, there is one failed in fivetimes, please have a check. thanks.

I will take a look

@jujiale please pull the latest changes, I have removed this test since it was irrelevant.

@jujiale please pull the latest changes, I have removed this test since it was irrelevant.
done. Thank you for your prompt reply


New landing page design

This is at mvp stage, we could certainly cleanup:

the CSS
the inline svg code (specifically resize to final dimensions to avoid aliasing)

Let’s be sure to sanity check:

All links
Browsers other than Chrome (including mobile)

Including some misc formatting edits to our README.
To test, navigate to docs/index.html.

Adjusted buttons per @yesnet0’s feedback
Put a max-height catch in for button that stretched vertically in IE
Added tag back to title
Removed _config.yml since we're no longer leveraging Jekyll

Result:

Feel free to make any further adjustments and merge, @dantrauner.


correctly encode/decode _FillValues/missing_values/dtypes for packed data

[x] Closes #7691
[x] Closes #5597
[x] Closes #2304
[x] Tests added
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst

This resurrects some of #7654. It takes special care of correctly handling dtypes when encoding/decoding packed data

Still an issue with some example in the docs. Probably non-conforming NaN _FillValue for packed data in that one example.

@kmankoff if you have time, can you check your workload against this PR, or review it please?

@mankoff if you have time, can you check your workload against this PR, or review it please?

It would be great if Ken could have a look here. At least I tried to follow the changes to CF which followed after the discussion in https://github.com/cf-convention/cf-conventions/issues/374.

On 2024-02-07 at 04:54 +13, Deepak Cherian @.***> wrote...

@mankoff if you have time, can you check your workload against this
PR, or review it please?

I'm reading this via slow satellite in Antarctica. I'm 'offline'(ish) for another week, then have 2 months of emails and work to catch up on. Reviewing this PR will be low priority.

I'm reading this via slow satellite in Antarctica. I'm 'offline'(ish) for another week, then have 2 months of emails and work to catch up on. Reviewing this PR will be low priority.

Thanks Ken, for letting us know. Greetings to Antarctica, hope time is good there! I'll try to ping some folks from the linked issues to get more input here.

@kmuehlbauer shall we merge? A number of numpy warnings (and presumably numpy 2 failures) are from this type of dtype maniputation. 🤞🏾 this PR fixes them all! :)

xarray/tests/test_conventions.py::test_decode_cf_with_conflicting_fill_missing_value
  /home/runner/work/xarray/xarray/xarray/conventions.py:286: SerializationWarning: variable 't' has non-conforming '_FillValue' nan defined, dropping '_FillValue' entirely.
    var = coder.decode(var, name=name)

should silence this warning

@dcherian I'm good to merge this, we still can iterate later if complaints are coming in.

@dcherian There are still some warnings which could be fixed/silenced with this PR. All try to get behind it now.

LGTM. Thanks!


Remove registration from Client?

I added this in the original design, but it doesn't fit with the static nature of the rest of the object.
I propose removing it, we can add it back later if needed, or something like client.getRegistration().
@mounirlamouri does this work for you?

lgtm. I actually did not notice this addition and it's not implemented so far ;)

Addressed: cf2e59a16483b3bec796a2f34f5728d4410df84a.

Closing.


Switch to TypeScript

For various reasons. But mainly, it's mainstream and well supported.

Therefore, the whole Este is being reimplemented. That's a good thing.

You can watch progress here https://github.com/este/este-typescript


Extended with go: Serving templates

Is there a way I can serve/parse  my own templates and  data in pocketbase ??

It is not clear what you are asking or trying to do, but you could check:

Go: https://pocketbase.io/docs/go-rendering-templates/
JSVM: https://pocketbase.io/docs/js-rendering-templates/

For other questions, please use the Q&A discussions instead but try to provide a little more details about your use case.