builder.buildStatic === No resolution found at all for condition...

Using<EMAIL_ADDRESS>with jspm@beta latest like this:
import path from 'path'
import Builder from 'systemjs-builder'

// is this the right way to load the configs i use for jspm 0.17 beta?
const builder = new Builder(__dirname,'./jspm.browser.js')
builder.loadConfig('./jspm.config.js')
.then(() => {
    builder.buildStatic('./app/tests/async-spec.js','./built.js', {format: 'esm'})
})

I am getting this error and stack when I try to buildStatic:
Unhandled rejection TypeError: No resolution found at all for condition circleup-circle/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/jspm_packages/github/jspm/nodelibs-process@0.2.0-alpha/#:./process.js.
    at /Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/systemjs-builder/lib/trace.js:637:15
    at Array.forEach (native)
    at /Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/systemjs-builder/lib/trace.js:630:6
    at tryCatcher (/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/bluebird/js/release/promise.js:497:31)
    at Promise._settlePromise (/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/bluebird/js/release/promise.js:555:18)
    at Promise._settlePromise0 (/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/bluebird/js/release/promise.js:600:10)
    at Promise._settlePromises (/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/bluebird/js/release/promise.js:683:18)
    at Async._drainQueue (/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/bluebird/js/release/async.js:125:16)
    at Async._drainQueues (/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/bluebird/js/release/async.js:135:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/Users/mnichols/dev/circleup/CircleUp-Main-Site/circle/static/circle/node_modules/bluebird/js/release/async.js:16:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

Yet this works when i run builder.bundle('./app/tests/async-spec.js','./built.js', {format: 'esm'})

This happens regardless of the module format I choose.
I verified that the path to<EMAIL_ADDRESS>exists
this script is running at the top level of my app

I am new to systemjs bundling and I am not sure how to back into solving this. Is my configuration loading correct for use with jspm@beta ? What am I doing wrong to get a static build?

Static builds need to be made for an exact environment - the browser or Node. So try setting browser: true or node: true accordingly in the build options.

You are da bomb. That fixed me up!. I looked on docs for that but I can't find that requirement anywhere stated. Is there another place than the README.md to be looking?


wine: failed to open "allredist/redist/2010/vcredist_x64.exe": c0000135

PLEASE READ THE REQUIREMENT BEFORE FILLING A BUG. ALSO PLEASE CHECK IF A SIMILLAR ISSUE ISN'T OPEN
Photoshop version
CC2021
Describe the bug
wine: failed to open "allredist/redist/2010/vcredist_x64.exe": c0000135
wine: failed to open "allredist/redist/2010/vcredist_x86.exe": c0000135
wine: failed to open "allredist/redist/2012/vcredist_x86.exe": c0000135
wine: failed to open "allredist/redist/2012/vcredist_x64.exe": c0000135
wine: failed to open "allredist/redist/2013/vcredist_x86.exe": c0000135
wine: failed to open "allredist/redist/2013/vcredist_x64.exe": c0000135
wine: failed to open "allredist/redist/2019/VC_redist.x64.exe": c0000135
wine: failed to open "allredist/redist/2019/VC_redist.x86.exe": c0000135
mkdir: cannot create directory ‘/home/alperen/PhotoshopCC2021/Adobe-Photoshop/drive_c/Program Files/Adobe’: File exists
mv: cannot stat 'allredist/photoshop.png': No such file or directory
To Reproduce
1: Start script by using sh photoshopcc2021.sh /home/username/
2: See the error
System informations

Distro : Arch linux
GPU : NVIDIA
WINE version : 8.8-1

The problem comes from the line 16 :
https://github.com/LinSoftWin/Photoshop-CC2022-Linux/blob/b43b0c62cb042de38f7bfc3524a115a2ad96af1c/scripts/photoshop2021install.sh#L16 when the script tries to download the Google Drive File
Host yourself the allredist.tar.xz, edit the script consequently and all will be fine ;)

Oh thx

It should be fixed, I've hosted them like the binaries.


Enable CUDA

faster experiment is important

turned out GPU is slower (much slower) for small matrixes, this is enabled but will now using cpu for testing.


Add 3 classes to School Library

This pull request adds 3 classes relevant to designing the school library app

Kindly note that using parent_permission = true produces a linters error as shown in the screenshot below.

Hence I used parent_permission: true instead as recommended by rubocop.
Thanks


[BUG] SQLite too many SQL variables

Describe the bug
A clear and concise description of what the bug is.
I'm getting an error after a while of using double-take (perhaps 1 week of double-take working fine) and the error is "too many SQL variables"
Version of Double Take
X.X.X-SHA7
Version 1.7.0
Expected behavior
A clear and concise description of what you expected to happen.
To work as normal but for a longer period
Screenshots
If applicable, add screenshots to help explain your problem.

Hardware

OS: [e.g. Ubuntu, macOS, Windows]
Browser (if applicable) [e.g. Chrome, Safari]

Double-take runs in a docker container
Additional context
Add any other context about the problem here.
Actual error as shown in the logs:
}
21-12-10 13:23:32 error: SqliteError: too many SQL variables
at Database.prepare (/double-take/api/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
at module.exports.get (/double-take/api/src/controllers/match.controller.js:97:6)
at newFn (/double-take/api/node_modules/express-async-errors/index.js:16:20)
at Layer.handle [as handle_request] (/double-take/api/node_modules/express/lib/router/layer.js:95:5)
at next (/double-take/api/node_modules/express/lib/router/route.js:137:13)
at /double-take/api/src/middlewares/index.js:42:5
at newFn (/double-take/api/node_modules/express-async-errors/index.js:16:20)
at Layer.handle [as handle_request] (/double-take/api/node_modules/express/lib/router/layer.js:95:5)
at next (/double-take/api/node_modules/express/lib/router/route.js:137:13)
at middleware (/double-take/api/node_modules/express-validator/src/middlewares/check.js:16:13)
21-12-10 13:30:25 error: SqliteError: too many SQL variables
at Database.prepare (/double-take/api/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
at module.exports.get (/double-take/api/src/controllers/match.controller.js:97:6)
at newFn (/double-take/api/node_modules/express-async-errors/index.js:16:20)
at Layer.handle [as handle_request] (/double-take/api/node_modules/express/lib/router/layer.js:95:5)
at next (/double-take/api/node_modules/express/lib/router/route.js:137:13)
at /double-take/api/src/middlewares/index.js:42:5
at newFn (/double-take/api/node_modules/express-async-errors/index.js:16:20)
at Layer.handle [as handle_request] (/double-take/api/node_modules/express/lib/router/layer.js:95:5)
at next (/double-take/api/node_modules/express/lib/router/route.js:137:13)
at middleware (/double-take/api/node_modules/express-validator/src/middlewares/check.js:16:13)

Having this same error, SQLite can be a pain in the ass if you're working with lots of data. Think the problem is caused when there are too many face detections in one photo which contains more data than you can put in a single row for SQLite (therefore the too many variables error). SQLite can be a big pain when working with large datasets, probably not a problem for most but I just had a large gathering at my house and loaded up Double Take to see this error. Simplest solution imo would be to just upgrade to postgres, but perhaps there's a reason that was avoided in development.


Encoding

This has been sitting for a few months because I couldn't find fastqs in the alternate encodings for test purposes. I think if we put in the docs that only sanger encoding has been thoroughly tested that might be ok. No idea where to get my hands on the others unless we're ok with me mocking them from scratch for test purposes.
Figure there's no sense in letting the branch continue to sit as I've stopped looking for real data in the alternate encodings.
Detecting is very straight-forward, either the PHRED scores are in the set of possible values or they aren't. For the purposes of this module, don't see any pitfalls of using mocked data.

Yes that would be good to point out. Also I think the only reason we even care is because it's a parameter in fastq_screen. I haven't figured out what FastQ-Screen uses it for, but as long as it's within a set that won't cause it to error, I don't think we care.

Yes that would be good to point out. Also I think the only reason we even care is because it's a parameter in fastq_screen. I haven't figured out what FastQ-Screen uses it for, but as long as it's within a set that won't cause it to error, I don't think we care.

This needs an addition to the docs page with, at minimum, links to the information on the various phred score ranges. Otherwise looks good. I did not test it, just reviewed the code.

This needs an addition to the docs page with, at minimum, links to the information on the various phred score ranges. Otherwise looks good. I did not test it, just reviewed the code.

@claymcleod @adthrasher I'm going to merge this unless either of you think BAM support is needed. Not sure if it can be easily done while using pysam, because pysam automatically decodes the PHRED scores (from the docs it seems it assumes the Sanger/Illumina1.8+ encoding. It's the most common and also what all our files use).

@claymcleod @adthrasher I'm going to merge this unless either of you think BAM support is needed. Not sure if it can be easily done while using pysam, because pysam automatically decodes the PHRED scores (from the docs it seems it assumes the Sanger/Illumina1.8+ encoding. It's the most common and also what all our files use).


bug: style mobile responsiveness of Home Page

fix #328

Summary by CodeRabbit

New Features

Improved styling for Autocomplete components for better centering.
Enhanced layout of the TemplateCard component for improved responsiveness.

Bug Fixes

Adjusted margins and spacing for better visual consistency.

Refactor

Streamlined Button click handler for improved readability.

@Aybrea : PR looks good to me. Thank you for your time!!


feat: big bang generate

Description
This adds a new feature zarf dev generate big-bang [Version]. It has been implemented according to the proposal here https://github.com/zarf-dev/proposals/pull/3
fixes #2875
Checklist before merging

[ ] Test, docs, adr added or updated as needed
[ ] Contributor Guide Steps followed

closing since this was moved into its own repo


Bump Inflex to 2.0

(Has a lot of fixes for pluralize.)
Tried to include ex_twilio in my project and it was conflicting due to older version of Inflex.  I was going to downgrade, but realized there are quite a few improvements in 2.0 for pluralize as well as the new parameterize_to_ascii which I am using in my project.
I experienced no breaks in my app and the ex_twilio test suite is still passing locally.

Thanks! :star: :star: :star:


Sonar fox homedir /var/run/sonar disappears on node boot, must be recreated

(This also ties into #309.)
When the node reboots, /var/run == /run is cleared, and /var/run/sonar goes away, and is not automatically created.  Then the sonar cronjobs will not run, and data will not be reported.  This is bad for any number of reasons.
There is a system for creating files in /run on reboot centered on /usr/lib/tmpfiles.d.
Alternatively if we use systemd and not cron to run sonar the service spec will contain information about how to create the necessary file structure.

This is becoming a headache.

This is now a nightmare.  A lot of fox nodes were rebooted and these all have this problem.

Going to make it /var/lib/sonar.

c1-16 and c1-21 pending, they are being serviced.  Otherwise all nodes done and appear to be reporting.  We need to:
mkdir /var/lib/sonar
chown sonar:sonar /var/lib/sonar
usermod --home /var/lib/sonar sonar
touch /etc/cron.d/sonar

Note, user must not be running anything for usermod to work, it will report an error if so - wait for the running sonar/exfil to die, or kill it.
Have also updated install files.

Fixed at last.

Also gpu-3...


fix changelog for a community pr

resolves #

Description
fix changelog

Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change

We will have to backport both these PRs just FYI to 1.0.latest if you want to do that earlier than later so we don't forget


update whatsapp app

Changes to a cask
Editing an existing cask

[ ] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.


Options file doesn't apply Forge 1.20.1

After saving all configs via /defaultsettings saveAll command and removing options.txt file, after restart mod only applies keybind settings, but lang and guy scale, as well as other options doesn't applies from mod DefaultSettings folder

This is intended behavior. If you ran those commands and delete the options.txt file afterwards, the mod will treat this as a local change of settings (as the ds_private_storage.json file knows that the options.txt file has already been created before). It won't interfere with it and thus those files will contain standard values.
If you want to ship the modpack, you must exclude the options.txt file AND the ds_private_storage.json file. To simulate that, you could locally delete both of these files. Then with the next startup the mod will set the correct settings.

OK, I would try and write to you afterwards

My bad, that's true: deleting ds_private_storage.json helps. Closing.

You're welcome :) Feel free to reopen in case you notice another issue with that particular feature.


Updated Nav Bar

Updated the nav bar and fixed the go back buttons.
PS: I think the nav bar can stay through all the pages since it increases navigational benefits for the user.

Thanks. Would love to see it merged and deployed :)

Thanks. Would love to see it merged and deployed :)

that is really amazing, buddy!

Hey @soumizde please make the navbar responsive , you forget to do that i think

Okay I am on it


unsafe_unicode

See: https://github.com/dart-lang/lints/issues/56

(WIP until the lint lands and the SDK is updated.)

@pq Can this be closed since it is going to be a hint in the SDK according to https://github.com/dart-lang/sdk/issues/47611?

Good catch.  This was implemented as a hint so we can safely close.  Thanks!


WASM/WASI threads support

What it's all about
This is my in-progress work in adding WASI threads support that is required for running LLVM-based .wasm modules built with threading support.
It also adds 2 env variables to enable threading features:

EXTISM_WASM_THREADS for WASM threads
EXTISM_WASI_THREADS for WASI threads

As a handy bonus, I've added EXTISM_DEBUG switch for enabling .debug_info().
Status
Currently, I have problems with implementing thread-safe wrappers over raw pointers used for input data (Internal.input) and plugin memory access (Internal.memory) propagation. It's required for spawn thread function coming from wasmtime-wasi-threads.
Also, there are some ownership conflicts with WasiThreadCtx, which wants to have ownership over module and linker for some reason, which is conflicting with local function ownership.
Once the issues above will be resolved, WASI threads should work as expected.
.NET-specific
To not mess with the existing NuGet while testing I'm publishing working changes to the new NuGet Extism.runtime.wasm-threads.win-x64 for local testing.
My thoughts
Maybe only threads-specific stores should have an Internal-like structure with safe pointers to not break everything? 🤔
Also, Internal is not quite a good name for such a structure, IMO. I propose something like InstanceContext. Then thread-specific struct will be InstanceThreadContext.

P.S. It's also worth bumping wasmtime dependencies versions, which I've already bumped in terms for the PR. Will revert if you have some sort of compatibility concerns.

Thanks - this looks good so far! I'm definitely open to some of your ideas surrounding InstanceContext and InstanceThreadContext.
Would it be easier to use Arc<Mutex<Internal>> (or RwLock) everywhere Internal is currently used instead of wrapping specific fields?
I'll keep digging into this a little more and will be sure to post any updates if I come up with anything.

Thanks!

InstanceContext and InstanceThreadContext
After looking a bit more into the codebase I found that InstanceCtx and InstanceThreadCtx are even more suitable (to be consistent with existing contexts structs naming).

Would it be easier to use Arc<Mutex<Internal>> (or RwLock) everywhere
I think it makes sense. 'll try to do so.

We will take another look at this for 1.0. In the meantime, @seclerp what was the intention and why did you need threads support?
I seem to recall it had something to do with dotnet on the guest side? if so we have a beta coming up for our dotnet pdk and it should support c# and f# https://github.com/extism/dotnet-pdk/pull/4

Hi @bhelx, it's great to hear that .NET PDK is coming. Yes, when I worked on that draft I tried experimenting with creating a .NET PDK based on the NativeAOT-LLVM project. However, I had no success because of Extism and NativeAOT-LLVM runtime restrictions and differences.

@seclerp sorry to hear that. We we keep this feature in mind for 1.0. We have been exploring supporting tokio and async rust for the runtime in https://github.com/extism/extism/issues/470 so that might make threads an easier feature to enable.  But if you have any feedback on our dotnet PDK, like whether or not it will work for you, that would be greatly appreciated.

Hi @bhelx, it's great to hear that .NET PDK is coming. Yes, when I worked on that draft I tried experimenting with creating a .NET PDK based on the NativeAOT-LLVM project. However, I had no success because of Extism and NativeAOT-LLVM runtime restrictions and differences.

@seclerp I am interested in learning more because NativeAOT-LLVM will probably produce much smaller binaries and the resulting plugins will be much faster than the embedded Mono method I went with in extism/dotnet-pdk#4

Since @seclerp is busy right now, he summons me. I do not know about specifcally his PDK experiment, but before that we play with NativeAOT-LLVM on bare Extism, so we can try from there. If you have questions interested about NativeAOT-LLVM I would try to answer to best of my knowledge.


[Feature] Add Black Hole Number Calculator

Description
Black Hole number Calculator is a simple fun calculator that takes whatever number you give and at last always the ends at four. Number 4 is referred to as Black Hole number because every word you spell will end in Four.
For Example :
User input : 6
6 in Words : Six
Count of Letters : 3
3 in Words : Three
Count of Letters : 5
5 in Words : Five
Count of Letters : 4
4 in Words : Four
Please assign me under  GSSOC'24
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[x] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Proceed @nilamkumari11


Changes are not reflecting instantly in Kivy

Hey there,
I need some guidance, I have just started using Kivy and facing a problem in UI.
I have a Button for which I want functionality like this:
button when clicked connect() function will be called and the Label showing the status will change to "connecting", and when the connection is done  the Label status will  change to the connected.
Here is the problem:
The Label directly converts to connected, it does not changes to the connecting and then to connected.
when the function is called in the beginning I am doing this:
Here is what I am doing:
when connecting starts:
self.ids.connect_button.text = "Connecting..."
once the connection is stablished:
self.ids.connect_button.text = "Connected"
The screen halts for a while and then directly converts to connected.
Even though there is some time gap but connecting does not appears.

Well I have tried with  threading and it helped me.


/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/parser.rst:270: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:27: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:38: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:53: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:61: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:79: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:85: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:89: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:124: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/security.rst:130: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:44: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:48: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:137: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:141: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:145: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:151: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:167: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:188: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:193: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:204: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:209: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:215: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:223: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:237: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:241: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:264: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:269: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:273: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:278: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:286: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:293: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:297: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:308: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:325: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:331: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:343: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:348: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:352: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:362: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:369: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:373: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:381: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:388: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:398: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:540: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:583: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:596: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:606: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:618: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:670: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:698: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:711: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:768: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/sessions.rst:1059: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:25: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:29: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:41: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:59: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:68: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:81: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:97: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:134: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:153: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:163: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:182: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:192: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:204: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:211: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:227: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:256: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:271: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/table.rst:285: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:28: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:32: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:40: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:76: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:109: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:120: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:145: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:180: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:185: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:199: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/trackback.rst:207: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/typography.rst:24: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/typography.rst:28: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/typography.rst:44: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/typography.rst:68: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/typography.rst:73: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/typography.rst:94: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/typography.rst:107: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:31: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:47: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:58: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:62: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:88: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:92: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:97: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:105: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:111: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:116: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:120: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:128: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:153: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/unit_testing.rst:162: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:36: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:49: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:53: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:84: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:116: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:121: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:132: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:139: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:168: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:180: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:184: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/uri.rst:218: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/user_agent.rst:27: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/user_agent.rst:48: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/user_agent.rst:86: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/user_agent.rst:108: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/user_agent.rst:183: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/user_agent.rst:195: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/user_agent.rst:205: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/user_agent.rst:228: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:49: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:56: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:80: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:119: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:126: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:152: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:196: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:215: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:269: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:276: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:298: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:317: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:358: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:396: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:412: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:435: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:478: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:482: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:491: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:504: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:515: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:540: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:550: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/xmlrpc.rst:563: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:25: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:29: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:39: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:62: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:75: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:86: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:96: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:112: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:124: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:134: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:145: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:165: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:176: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:193: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:203: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:217: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/libraries/zip.rst:232: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/overview/at_a_glance.rst:55: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/overview/at_a_glance.rst:83: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/overview/at_a_glance.rst:91: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/create_news_items.rst:21: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/create_news_items.rst:53: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/create_news_items.rst:103: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/create_news_items.rst:144: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:24: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:44: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:63: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:91: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:130: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:148: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:173: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:196: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/news_section.rst:212: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/static_pages.rst:32: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/static_pages.rst:61: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/static_pages.rst:77: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/static_pages.rst:98: WARNING: Pygments lexer name 'ci' is not known
/home/ignacio/Downloads/CodeIgniter-develop/user_guide_src/source/tutorial/static_pages.rst:152: WARNING: Pygments lexer name 'ci' is not known
generating indices... genindex
writing additional pages... search
copying images... [100%] overview/../images/appflowchart.gif
copying downloadable files... [100%] documentation/ELDocs.tmbundle.zip
copying static files... done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 1084 warnings.

The HTML pages are in build/html.
Build finished. The HTML pages are in build/html.

This is a support issue, not a bug!
The error messages sugest that your ci_lexer is not properly setup.
For further help, ask on the forum, thanks.


[SPARK-46908] Support star clause in WHERE clause

What changes were proposed in this pull request?

Extend star clause from the Project to Filter
Treat (*) as a row value constructor, rather than a no-op
Support IN(*)

Why are the changes needed?

This PR simplifies the writing of queries by bringing the popular shorthand to more scenarios.
For example one can write:
WHERE coalesce(* EXCEPT(pk)) IS NOT NULL to remove "null rows") or
WHERE foo(t.*) = true to pass all columns from a table to a function
Does this PR introduce any user-facing change?

Yes
How was this patch tested?

New tests in selectExcept
Was this patch authored or co-authored using generative AI tooling?

No

@gengliangwang @cloud-fan

All comments addressed. This PR is ready to merge once it's done with QA cycle.
@cloud-fan

@srielau +1 for the proposal! It would be great if we could mention the change in https://github.com/apache/spark/blob/master/docs/sql-migration-guide.md as well.

@srielau +1 for the proposal! It would be great if we could mention the change in https://github.com/apache/spark/blob/master/docs/sql-migration-guide.md as well.

Done @gengliangwang

thanks, merging to master!


PASSTHROUGH mode for ingress gateway does not work

Bug description
Has there been any change in the use of the PASSTHROUGH mode for gateways? The exact set of resources (that is, Istio gateway, vs, and dr) which were working fine with 1.4.* do not work anymore. The traffic gets directed to destination pod through the port  15443 but the request fails with no healthy upstream error. I do not use *.global and do not need the rewrite.
requests get top the service but eventually fail with 503 and "no healthy upstream"
The same exact resources works fine with Istio 1.4.2
Expected behavior
Using PASSTHROUGH with a VS to get to a service
Steps to reproduce the bug
apiVersion: networking.istio.io/v1beta1
  kind: Gateway
 metadata:
  name: helloworld-gateway
  spec:
    selector:
      istio: ingressgateway
    servers:
    - hosts:
      - helloworld.default.svc.cluster.local
      port:
        name: helloworld
        number: 15443
        protocol: TLS
      tls: {}
---
 apiVersion: networking.istio.io/v1beta1
  kind: VirtualService
  spec:
    gateways:
    - helloworld-gateway
    hosts:
    - '*'
    tls:
    - match:
      - port: 15443
        sniHosts:
        - helloworld.default.svc.cluster.local
      route:
      - destination:
          host: helloworld.default.svc.cluster.local
          port:
            number: 5000
          subset: notls
---
  apiVersion: networking.istio.io/v1beta1
  kind: DestinationRule
  spec:
    host: helloworld.default.svc.cluster.local
    subsets:
    - name: notls
      trafficPolicy:
        tls: {}
    trafficPolicy:
      tls:
        mode: ISTIO_MUTUAL

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
$ istioctl version
client version: 1.6.0-rc.0
control plane version: 1.6.0-rc.0
data plane version: 1.6.0-rc.0 (6 proxies)

How was Istio installed?
istioctl manifest apply \
         -f manifests/examples/multicluster/values-istio-multicluster-gateways.yaml

Environment where bug was observed (cloud vendor, OS, etc)

Note that while PASSTHROUGH does not work, AUTHO_PASSTHROUGH works as expected.


[Bug]: Registering a pandas df does no longer work with sqlalchemy >=2

What happened?
Can't register dataframes for as specified in https://github.com/Mause/duckdb_engine#how-to-register-a-pandas-dataframe with sqlalchemy>=2.
with engine.connect() as conn:
    conn.execute("register", ("df", df)) <--- stack trace in relevant log output
    conn.execute(f"INSERT INTO {table_name} SELECT * FROM df")

Works when downgrading to sqlalchemy==1.4
(Might just need a doc update?)
DuckDB Engine Version
0.9.0
DuckDB Version
0.9.2
SQLAlchemy Version
2.0.21
Relevant log output
/Users/***/Documents/projects/project/.venv/lib/python3.10/site-packages/duckdb_engine/__init__.py:162: DuckDBEngineWarning: duckdb-engine doesn't yet support reflection on indices
  warnings.warn(
Traceback (most recent call last):
  File "/opt/homebrew/Caskroom/miniconda/base/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/homebrew/Caskroom/miniconda/base/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/Users/***/.vscode/extensions/ms-python.python-2023.16.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/__main__.py", line 39, in <module>
    cli.main()
  File "/Users/***/.vscode/extensions/ms-python.python-2023.16.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py", line 430, in main
    run()
  File "/Users/***/.vscode/extensions/ms-python.python-2023.16.0/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher/../../debugpy/../debugpy/server/cli.py", line 284, in run_file
    runpy.run_path(target, run_name="__main__")
  File "/Users/***/.vscode/extensions/ms-python.python-2023.16.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 321, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "/Users/***/.vscode/extensions/ms-python.python-2023.16.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 135, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/Users/***/.vscode/extensions/ms-python.python-2023.16.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_runpy.py", line 124, in _run_code
    exec(code, run_globals)
  File "/Users/***/Documents/projects/project/scripts/duckdbify.py", line 170, in <module>
    asyncio.run(main())
  File "/opt/homebrew/Caskroom/miniconda/base/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/opt/homebrew/Caskroom/miniconda/base/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/Users/***/Documents/projects/project/scripts/duckdbify.py", line 166, in main
    export_to_duck(df_tables, junction_tables, engine)
  File "/Users/***/Documents/projects/project/scripts/duckdbify.py", line 102, in export_to_duck
    create_table(table_name, df, constraints=[PrimaryKeyConstraint('id')], engine=engine)
  File "/Users/***/Documents/projects/project/scripts/duckdbify.py", line 89, in create_table
    conn.execute("register", ("df", df))
  File "/Users/***/Documents/projects/project/.venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1406, in execute
    distilled_parameters = _distill_params_20(parameters)
  File "lib/sqlalchemy/cyextension/util.pyx", line 26, in sqlalchemy.cyextension.util._distill_params_20
  File "lib/sqlalchemy/cyextension/util.pyx", line 17, in sqlalchemy.cyextension.util._check_item
sqlalchemy.exc.ArgumentError: List argument must consist only of tuples or dictionaries

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey there! Yes this is a docs issue, in sqlalchemy 2 you have to use the exec_driver_sql instead, see here: https://github.com/Mause/duckdb_engine/blob/f92dc4dcd2869d6161d778c672ebf8750f2455f7/duckdb_engine/tests/test_integration.py#L12


Dikastes: use gRPC graceful shutdown to exit cleanly after getting signal

I've come across an issue when using Dikastes sidecar in a kubernetes job.
I needed to manually send SIGTERM to the process otherwise my pod would never be marked as Completed (all containers inside the pod need to be terminated). This worked but dikastes usually returned non-zero exit code due to the gRPC server terminating abruptly. Calling the GracefulStop library function fixed it for me and I believe it is a good practice to use it anyway.

/sem-approve


Removing warnings of no property initialization on dev server

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


Null value return 0 Instead Null

DB Table Value

Select Query Result

Did this bug ? Null will replaced into 0 ?
If I want to get null value instead 0 ?
Packages :
"@op-engineering/op-sqlcipher": "^2.0.3",
"react": "18.2.0",
"react-native": "0.72.6",

Looks correct to me. You should try to create a minimal reproducible example

Still giving me the same result. newest release package give me error openssl-config.cmake

If you are having an issue with sqlcipher, create an issue in the repo. Also, create a reproducible example, I already tried to reproduce it and found no issues, don't have time to create a project from scratch and find the cause.

Hi @shiroze.
I got this error too, with async methods, on android.
I've send a PR and i'm waiting for review now. If it gets accepted, could you check your use case again?

Hi @shiroze. I got this error too, with async methods, on android. I've sent a PR and i'm waiting for review now. If it gets accepted, could you check your use case again?

I ran into the same issue without using op-sqlcipher.  I ended up just reverting back to the old repo for now.  I can test the PR as well.

Hi @shiroze. I got this error too, with async methods, on android. I've sent a PR and i'm waiting for review now. If it gets accepted, could you check your use case again?

I ran into the same issue without using op-sqlcipher. I ended up just reverting back to the old repo for now. I can test the PR as well.

Nice, this is the PR:
https://github.com/OP-Engineering/op-sqlite/pull/48
The null fix is among others small fixes.

Sorry, I've been traveling the last days. Will take a look soon

Hi @shiroze!
Did you had the time to test this problem with the 2.0.18 release?

Hi @shiroze! Did you had the time to test this problem with the 2.0.18 release?

Sorry for late reply and yes, already tested and it give me the result I want.
thank you


This page (migration from .NET Framework 4.6.1 to 4.7.1) should mention System.Runtime and some other system assemblies which are changed in .NET 4.7.1...

Here is a few GitHub issues.
https://github.com/dotnet/corefx/issues/32757
https://github.com/dotnet/standard/issues/481
System.Runtime and some other system assemblies are integrated in .NET framework 4.7.1. It brings some weird issues for the apps developed with .NET framework 4.6.1 and then upgraded to .NET 4.7.1. Those apps used NuGet packages for System.Runtime with .NET framework 4.6.1 and could start to fail after the migration to .NET 4.7.1.

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

ID: 4e0c50e8-ca91-7949-1667-ea1630ec8f0b
Version Independent ID: ad795371-4b90-51d3-0b9e-711e77945831
Content: Runtime Changes for Migration from .NET Framework 4.6.1 to 4.7.1
Content Source: docs/framework/migration-guide/runtime/4.6.1-4.7.1.md
Product: dotnet-framework
Technology: dotnet-appcompat
GitHub Login: @chlowell
Microsoft Alias: ronpet

Thanks for your feedback, @zxli. Offhand, though, it strikes me that this is an issue that relates to IDE tooling rather than to the .NET Framework itself. @PriyaPurkayastha, what do you think?

I agree with Ron's assessment that this is not a breaking change between .NET 4.6.1 to 4.7.1 based on this resolution provided for GitHub issue dotnet/corefx#32757 mentioned in this issue at the beginning:
The problem here I believe is with the VS tooling when you add the nuget package reference. It shouldn't be adding that extra binding redirect. If you instead migrate your project to use PackageReference then installing a new package won't generate binding redirects, and only at build time will we figure out if you need extra binding redirects or not, which in this case you shouldn't need any for System.Runtime as it already comes inbox for 4.7.1.
The .NET 4.7.1 release announcement blog has a section for "BCL - .NET Standard 2.0 section" which talks about this at:
https://devblogs.microsoft.com/dotnet/announcing-the-net-framework-4-7-1/

Closing this issue since it's not a .NET Framework breaking change.


New version: SmartGameBooster.SmartGameBooster version 5.2.3

- [X] Have you signed the Contributor License Agreement?

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: Open in CodeFlow

From my latest scan -

https://www.pcgameboost.com/download.php for SmartGameBooster.SmartGameBooster version 5.2.1 redirects to https://download.itopupdate.com/dl/smartgb/smart_game_booster_setup.exe

@wingetbot waivers Add Validation-Domain


integration of FSR shader for sharper render scaling

FSR shader courtesy of Zyko:
https://gist.github.com/Zyko0/0b9244d6780eeb2337162c6dbdf9b787

I've decided to go with the only selections being off or 2x, since there wasn't any noticeable gain from 3x/4x.


Unable to record YouTube livestreams while --embed-subs is set

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a site-specific feature
[X] I've verified that I'm running yt-dlp version 2023.03.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
No response
Example URLs
https://www.youtube.com/watch?v=jfKfPfyJRdk
Provide a description that is worded well enough to be understood
I often want subtitles (if they are available) embedded into the output file, so I decided to add --embed-subs to yt-dlp's config file to automate this.
Unfortunately, this comes with a side effect: Unless explicitly overwritten with --no-embed-subsI'm unable to record/download YouTube livestreams or premieres, ass yt-dlp tries to download the live chat before capturing the video. Since, obviously, new chat messages will drop in every second, yt-dlp never starts actually recording recording.
yt-dlp also tells that
WARNING: Live chat download runs until the livestream ends. If you wish to download the video simultaneously, run a separate yt-dlp instance

so it's more a enhancement request than a bug report, but I don't see how this outcome is expected or intended.
So, while I get that this is partly my fault by adding --embed-subs to the config, I'd suggest to either handle the live chat not as subtitles at all (because they aren't), or at least record them simultaneously with the video.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://www.youtube.com/watch?v=jfKfPfyJRdk']
[debug] User config "/Users/xxx/.config/yt-dlp/config": ['--force-ipv4', '--format', 'bestvideo[vcodec^=avc1]+bestaudio[ext=m4a]/bestvideo+bestaudio/best', '--embed-chapters', '--embed-subs', '--embed-metadata', '--fixup', 'never']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[01aba2519] (zip)
[debug] Python 3.11.4 (CPython arm64 64bit) - macOS-13.4-arm64-arm-64bit (OpenSSL 1.1.1u  30 May 2023)
[debug] exe versions: ffmpeg N-110783-g29710dd7f2 (setts), ffprobe N-110783-g29710dd7f2, phantomjs 2.1.1
[debug] Optional libraries: certifi-2023.05.07, pycrypto-3.17, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {}
[debug] Loaded 1845 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 6774b889af8aec948511256bde94834063bb4729ea1e0a89a5b79e38a71e3593
yt-dlp is up to date<EMAIL_ADDRESS>[youtube] Extracting URL: https://www.youtube.com/watch?v=jfKfPfyJRdk
[youtube] jfKfPfyJRdk: Downloading webpage
[youtube] jfKfPfyJRdk: Downloading android player API JSON
[youtube] jfKfPfyJRdk: Downloading m3u8 information
[youtube] jfKfPfyJRdk: Downloading m3u8 information
[info] jfKfPfyJRdk: Downloading subtitles: live_chat
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[info] jfKfPfyJRdk: Downloading 1 format(s): 96
[info] Writing video subtitles to: lofi hip hop radio 📚 - beats to relax⧸study to 2023-06-18 15_43 [jfKfPfyJRdk].live_chat.json
[debug] Invoking youtube_live_chat downloader on "https://www.youtube.com/watch?v=jfKfPfyJRdk&bpctr=9999999999&has_verified=1"
[youtube_live_chat] Downloading live chat
WARNING: Live chat download runs until the livestream ends. If you wish to download the video simultaneously, run a separate yt-dlp instance
[youtube_live_chat] Total fragments: unknown (live)
[download] Destination: lofi hip hop radio 📚 - beats to relax⧸study to 2023-06-18 15_43 [jfKfPfyJRdk].live_chat.json
[download]    1.39MiB at  931.54KiB/s (00:00:00) (frag 2)

Add --compat-options no-live-chat to your config. Perhaps that should be added to the warning.

at least record them simultaneously with the video

I don't think that's currently possible, hence the warning

handle the live chat not as subtitles at all

Uh, but then we have to add a --write-live-chat option. Although like I've previously suggested, perhaps we should replace all the --write options with a single option that accepts a parameter. So for example, to download subtitles and thumbnails you could run --write subs,thumbnails. That option could treat live chat as not subtitles, and --write-subs could continue to treat live chat as subtitles, but be deprecated (no longer documented).
I don't know how feasible my suggestion is though


Add Excel file to cache in test

Description:

Fixes #49
Before using the Excel parser, the Excel file must have been downloaded and stored in the data cache.
This was previously not the case, but this fix implements that pre-storage.
Type of change:

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

Checklist for the reviewer:

This checklist should be used as a help for the reviewer.

[ ] Is the change limited to one issue?
[ ] Does this PR close the issue?
[ ] Is the code easy to read and understand, including clearly named variables?
[ ] Do all new feature have an accompanying new test?
[ ] Has the documentation been updated as necessary?

@jesper-friis I will just force this through now to make way for the other waiting PRs. If other issues should arise, new issues and fixes can be implemented.


some vtt parse crash

英語語音學一.01..Class.Overview.(2020.updated).txt

This file is wild.  Loads of empty cues, cues containing only a single space, cues that are duplicated 10ms later, cues that contain only a single space character. Was it automatically generated?
For example :-
00:51:49.829 --> 00:51:49.839 align:start position:0%
there are some readings in some of those

00:51:49.839 --> 00:51:52.470 align:start position:0%
there are some readings in some of those
languages<00:51:50.400><c> below</c><00:51:50.880><c> i</c><00:51:51.040><c> have</c><00:51:51.200><c> a</c><00:51:51.280><c> couple</c><00:51:51.520><c> of</c><00:51:51.680><c> jokes</c>

00:00:45.830 --> 00:00:45.840 align:start position:0%
probably more times i saw him once in

00:00:45.840 --> 00:00:47.350 align:start position:0%
probably more times i saw him once in
taiwan

The issue was that I was trimming lines of whitespace, which would nuke some of the cue entries that contained only a single space (?). The code logic made an assumption regarding the length of an array and as such busted.
Grab the latest build (1.8.2) which should resolve the issue.
Please let me know how you go.

No problem, thank you for your reply.
This file was downloaded from a website, and I’m not sure how the original author generated it. It definitely looks messy.
Thanks for the quick fix, I will test it as soon as possible.

Sorry for the late reply. I can confirm that the fix resolved the crash issue. However, since this file doesn’t seem to be standard, there are some issues with the parsed subtitles. It could be that there’s an issue with the current parsing implementation, or perhaps more fault tolerance is needed.
I tried importing the file into the iOS Files app, and it parsed and worked correctly in the preview. Here’s a screenshot.
https://github.com/user-attachments/assets/021ed628-5761-4bb9-b90e-0372d4787604
and<00:00:18.400><c> we'll</c><00:00:18.560><c> go</c><00:00:18.720><c> to</c><00:00:18.880><c> the</c><00:00:18.960><c> web</c><00:00:19.119><c> page</c><00:00:19.359><c> in</c><00:00:19.520><c> a</c><00:00:19.600><c> minute</c>

These seems should be ignored.

Hey @Josscii good news on the crash.
If you have concerns with the vtt importer can you raise another issue and close this one? That way the issue doesn't morph away from its original intent.


backend container on dev-env is exiting

PS C:\Users\91916\Desktop\temp\medbucket> docker ps -a
CONTAINER ID        IMAGE                 COMMAND                  CREATED             STATUS                       PORTS                                                 NAMES
4a44ffd424e4        backend:latest        "/start-reload.sh"       10 seconds ago      Exited (127) 8 seconds ago                                                         medbucket_backend_1
cc4f81eb2d88        celeryworker:latest   "bash /worker-start.…"   10 seconds ago      Up 8 seconds                                                                       medbucket_celeryworker_1
00dbca62b721        dpage/pgadmin4        "/entrypoint.sh"         10 seconds ago      Up 8 seconds                 80/tcp, 443/tcp, <IP_ADDRESS>:5050->5050/tcp               medbucket_pgadmin_1
2d68bd813966        traefik:v2.2          "/entrypoint.sh --pr…"   11 seconds ago      Up 9 seconds                 <IP_ADDRESS>:80->80/tcp, <IP_ADDRESS>:8090->8080/tcp            medbucket_proxy_1
b1a22f8a2415        mher/flower           "flower --broker=amq…"   11 seconds ago      Up 9 seconds                 <IP_ADDRESS>:5555->5555/tcp                                medbucket_flower_1
bfe9f77e6280        postgres:12           "docker-entrypoint.s…"   11 seconds ago      Up 9 seconds                 5432/tcp                                              medbucket_db_1
691ede2a4b1b        frontend:latest       "nginx -g 'daemon of…"   11 seconds ago      Up 9 seconds                 80/tcp                                                medbucket_frontend_1
612968ab517a        rabbitmq:3            "docker-entrypoint.s…"   11 seconds ago      Up 9 seconds                 4369/tcp, 5671-5672/tcp, 15691-15692/tcp, 25672/tcp   medbucket_queue_1
PS C:\Users\91916\Desktop\temp\medbucket> docker-compose logs backend
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
Attaching to medbucket_backend_1
backend_1       | Checking for script in /app/prestart.sh
backend_1       | Running script /app/prestart.sh
: not found     | /start-reload.sh: 2: /app/prestart.sh:

The backend container is exiting after docker-compose up. I am running the container set up on my development environment
did anyone else face this issue before?

what does the containers log say? when i faced this is was either due to pgsql not yet started or started, but data dir contained files.

logs for backend
PS C:\Users\91916\Desktop\temp\medbucket> docker-compose logs backend
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
Attaching to medbucket_backend_1
backend_1       | Checking for script in /app/prestart.sh
backend_1       | Running script /app/prestart.sh
: not found     | /start-reload.sh: 2: /app/prestart.sh:

DB logs
PS C:\Users\91916\Desktop\temp\medbucket> docker-compose logs db
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
WARNING: The following deploy sub-keys are not supported and have been ignored: labels
Attaching to medbucket_db_1
db_1            |
db_1            | PostgreSQL Database directory appears to contain a database; Skipping initialization
db_1            |
db_1            | 2021-04-05 07:40:00.771 UTC [1] LOG:  starting PostgreSQL 12.6 (Debian 12.6-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
db_1            | 2021-04-05 07:40:00.776 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
db_1            | 2021-04-05 07:40:00.776 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1            | 2021-04-05 07:40:00.791 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1            | 2021-04-05 07:40:00.960 UTC [25] LOG:  database system was interrupted; last known up at 2021-04-04 13:36:20 UTC
db_1            | 2021-04-05 07:40:01.360 UTC [25] LOG:  database system was not properly shut down; automatic recovery in progress
db_1            | 2021-04-05 07:40:01.365 UTC [25] LOG:  redo starts at 0/16763E8
db_1            | 2021-04-05 07:40:01.366 UTC [25] LOG:  invalid record length at 0/16764D0: wanted 24, got 0
db_1            | 2021-04-05 07:40:01.366 UTC [25] LOG:  redo done at 0/1676498
db_1            | 2021-04-05 07:40:01.427 UTC [1] LOG:  database system is ready to accept connections

do you know where the db-data folder is created?

My issue got resolved after changing the line endings in s code from CRLF to LF
https://github.com/tiangolo/full-stack-fastapi-postgresql/issues/41

Thanks for the help @haviduck ! :coffee:
Thanks for reporting back and closing the issue @we-shall  👍

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Provide provenance info for ion parameters

@slochower noticed that there is no record of where the monovalent ion paramters come from in this line of FFs. He suggested that they probably come from Jeong and Cheatham. Let's:

Confirm that these are our ion parameters
Modify the 1.0.0 release notes to indicate as much.

I spot checked Na⁺ and Cl- and they match frcmod.ionsjc_tip3p distributed with AMBER18. I have not further investigated, yet.

I believe i took these from the Jeong-Cheatham parameters, specifically that file. But it's worth checking -- I probably documented it in a pull request somewhere but cannot easily find it.

That looks correct to me. I suggest this is documented somewhere (I didn't think to search PRs, or at least, I'm not sure if GitHub default searches in PR comments) as I spent a little while this morning trying to find their origin (and we should be completely transparent about this). :)


Provide reqwest::post function?

The reqwest::get function is very convenient. Any reason why there isn't a similar function for http POST? (or any other HTTP method?)

reqwest::get exists mostly for simple demos (and the rare case that some CLI or other application needs to make a single default GET request). It doesn't allow customizing the options or setting any headers or body etc.
What do you propose post et al would do? Post with or without a body?

What do you propose post et al would do? Post with or without a body?

I would expect the function to return a RequestBuilder so that I can do all the things I can do on a Client instance as-well.
To be fair, I only noticed after writing this issue that there is a subtle difference between reqwest::get and Client::get as in the former one implies send.
What I like about the API is that I don't have to instantiate a Client myself. I am not sure how expensive that actually is (the one within reqwest::get is dropped afterwards right?).
What I would expect from reqwest::post etc APIs is that I don't have to instantiate a Client but still can configure the request for common scenarios (body & headers mostly).


Documentation or instructions?

Is there a guide on how a new person can get started after installing?  What is created first, the model or the bot?  What do the different pages mean?  What do we do about errors when trying to communicate with RSA NLU?  The Wiki says to find "beta" in the branches, but there is only a "master" branch. Is the master v3?  What is the red server icon on the top right?  There is no tooltip or any help on the UI, so not sure what some of these fields mean (server path to model file?  what's a server path look like in that field?)

@samboustani  Did you find any?


Use float64 instead of float32 for metrics of Float type

What this PR does
Cherry-pick PR #1975 to release 1.5

/lgtm


More snapshot abstraction

What have you changed?
This restructures some of the engine_traits traits to avoid recursive associated types, and then pulls up more of the snapshot abstractions through generic tikv functions. After this PR, considerably more of tikv is parameterized over engines.
Fixes https://github.com/tikv/tikv/issues/6124
Part of https://github.com/tikv/tikv/issues/4184
To avoid situations like:
trait KvEngine {
    type Snapshot: Snapshot;
}

trait Snapshot {
    type KvEngine: KvEngine
}

which result in generics that can't be typechecked because the two KvEngine instances can't be proved the same, "branch" traits are instead parameterized over their "parent" traits, like
trait KvEngine {
    type Snapshot: Snapshot;
}

trait Snapshot<E> where E: KvEngine { }

And then implementations only implement the traits for their concrete types like
impl Snapshot<RocksEngine> for RocksSnapshot { }

What is the type of the changes?

Engineering (engineering change which doesn't change any feature or fix any issue)

How is the PR tested?
cargo test --all --no-run
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
Does this PR affect tidb-ansible?
Refer to a related PR or issue link (optional)
https://github.com/tikv/tikv/issues/6124
https://github.com/tikv/tikv/issues/4184
Benchmark result if necessary (optional)
Any examples? (optional)

/test

Updated. Comments addressed.

/test

Merge conflicts resolved.

/merge


fix: Do not call create collection as this fails when the collection already exists

@funkenstrahlen Did you already publish the change as a new version of the package db-migrate-mongodb-nesto-fork?


feat: made social anchors accessible on contact us page ✨

Related Issue
Close #1040
Description

Added aria-label attribute for social anchors like github & twitter
The aria-label attribute is important for screen readers because it provides a text label for an object, such as a with social icons. When a screen reader encounters the object, the aria-label text is read so that the user will know what it is.
This is important for people who are blind or have low vision, as they rely on screen readers to access the web.
Improved title attribute's data, because the title attribute is intended to provide additional information to screen reader users.
And along with that i added rel for the anchors which are lacking them to ensure best practices for crawlers
Because adding the rel="noopener noreferrer" attribute can help to protect this website from security vulnerabilities and improve performance. It is a good practice to use this attribute on all external links.
Overall this PR is intended to make necessary changes to meet best practices for crawlers along with improving accessibility for social anchors

Screenshots

We can't take screenshots of accessibility changes rather than code changes, Accessibility changes are often invisible to the user because it's intended to guide disabled people

Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

Hey there @crocmons, @rohansx 👋🏻
Please make sure to review this PR with level2 label because this PR is about adding new feature related accessibility.
Thank you.


efficient way to send multiple request

Hi again,
I want to download a weekly pattern for a particular naics_code (school) over time. However, there are 126000 unique place keys for schools in the database. I write down a code to iterate one by one and send a request, but I got
HTTPError: 429 Client Error: Too Many Requests... error
What is the efficient way to request a lookup without causing problems? I download the monthly data from the Safegraph shop but I guess sending too many requests would not be efficient.
Thank you for the help.

Hey @aghalandar for getting multiple records from a single naics, the search() function would be the way to go. However, 126k is a lot of records, and the API's not at the point yet where it can handle requests of that size. We're working on it.
How much history do you need?
We created a temporary endpoint for bulk weekly_patterns downloads that'll let you get all Patterns for all places in the US. You can loop over that by date and filter down to just the schools. It returns 500 placekeys at a time, and you can feed in the most recently returned placekey to paginate through the dataset. It'll be a lot of data, but it's the quickest way using our API at the moment to get large amounts of data.
cc @MTaylor24
query AcademicBulkWeeklyPatterns(
  $date: DateTime!
  $iso_country_code: String
  $last_seen_placekey: String
) {
  bulk_weekly_patterns(
    date: $date
    iso_country_code: $iso_country_code
    last_seen_placekey: $last_seen_placekey
  ) {
    placekey
    parent_placekey
    location_name
    street_address
    city
    region
    postal_code
    iso_country_code
    safegraph_brand_ids
    brands
    date_range_start
    date_range_end
    raw_visit_counts
    raw_visitor_counts
    visits_by_day
    visits_by_each_hour
    poi_cbg
    visitor_home_cbgs
    visitor_home_aggregation
    visitor_daytime_cbgs
    visitor_country_of_origin
    distance_from_home
    median_dwell
    bucketed_dwell_times
    related_same_day_brand
    related_same_week_brand
    device_type
  }
}

Hey @e-chong
Thank you for the response. I know! it is a lot. I prefer it mass-download the data from the shop and apparently, the weekly pattern is not available.
thank you for the solution. I want to run the new code; However, when I  start the code again, after
sgql_client = sgql.HTTP_Client(apikey)
I still get the following error:
HTTPError: 429 Client Error: Too Many Requests for url: https://api.safegraph.com/v1/graphql
I also get a new API key, but I get the same error.

Hey @aghalandar ah, we have a rate limit on for users right now as we're working through beta.
Can you email your apikey and the email address you used to register to eugene at safegraph dot com? I will get you whitelisted.

I add to your code the following as queri variable :
{ "date": "2021-07-26",
"iso_country_code": "US",
"last_seen_placekey": "zzw-225@5sb-86x-vs5"
}
When I run the code, I get the following error:
{
"errors": [
{
"message": "Cannot query field 'bulk_weekly_patterns' on type 'Query'. Did you mean 'supplemental_patterns'? (line 7, column 3):\n{ bulk_weekly_patterns(\n  ^",
"locations": [
{
"line": 7,
"column": 3
}
]
}
]
}

@aghalandar can you post the exact full query that you tried to use?

sorry @aghalandar , I see the issue. I forgot to mention in my first message that that Query type uses a different endpoint.  Please use https://placesapi.safegraph.com/v1/graphql/bulk instead of https://placesapi.safegraph.com/v1/graphql/.

Now, I change the endpoint. My code is as follows:
from sgqlc.endpoint.http import HTTPEndpoint
url = 'https://placesapi.safegraph.com/v1/graphql/bulk'
headers = {'Authorization': ' my tocken here'}
endpoint = HTTPEndpoint(url, headers)
query = '''query {
lookup(placekey: "222-224@5vg-7gr-6kz") {
placekey
safegraph_core {
location_name
street_address
city
region
postal_code
iso_country_code
}
}
}'''
data = endpoint(query)
I just want to check a simple query and I get the error:
https://placesapi.safegraph.com/v1/graphql/bulk: HTTP Error 401: Unauthorized
I also cannot use the SafegraphQl anymore since I have to change the endpoint. I am not sure how I can change the endpoint in safegraphQL.

Hey @aghalandar, sorry for the confusion here.
The "bulk" endpoint works only with the AcademicBulkWeeklyPatterns query type shown below, and it is not supported by the safegraphQL library. In short, this is b/c AcademicBulkWeeklyPatterns is a temporary solution we created to support bulk queries like the one you're trying to do while we fix up some things on the backend that will let us support those queries on the regular endpoint.
The gql library is what we built the safegraphQL library on top of, and that might be helpful for you constructing this query: https://github.com/graphql-python/gql
I'll also ask some of our other academic community members who've been using this endpoint if they have some code to share that would be helpful for you.
Appreciate your patience here.
query AcademicBulkWeeklyPatterns(
  $date: DateTime!
  $iso_country_code: String
  $last_seen_placekey: String
) {
  bulk_weekly_patterns(
    date: $date
    iso_country_code: $iso_country_code
    last_seen_placekey: $last_seen_placekey
  ) {
    placekey
    parent_placekey
    location_name
    street_address
    city
    region
    postal_code
    iso_country_code
    safegraph_brand_ids
    brands
    date_range_start
    date_range_end
    raw_visit_counts
    raw_visitor_counts
    visits_by_day
    visits_by_each_hour
    poi_cbg
    visitor_home_cbgs
    visitor_home_aggregation
    visitor_daytime_cbgs
    visitor_country_of_origin
    distance_from_home
    median_dwell
    bucketed_dwell_times
    related_same_day_brand
    related_same_week_brand
    device_type
  }
}

Thank you for your help and support. That would be great.
I am not very advance in python.

@aghalandar are you comfortable using curl? The below should work - you just need to update the date and last_seen_placekey and change YOUR_API_KEY to loop through the data.
curl 'https://api.safegraph.com/v1/graphql/bulk' -H 'Accept-Encoding: gzip, deflate, br' -H 'Content-Type: application/json' -H 'Accept: application/json' -H 'Connection: keep-alive' -H 'DNT: 1' -H 'Origin: https://places-api.safegraph.io' -H 'apikey: YOUR_API_KEY' --data-binary '{"query":"query AcademicBulkWeeklyPatterns(\n  $date: DateTime!\n  $iso_country_code: String\n  $last_seen_placekey: String\n) {\n  bulk_weekly_patterns(\n    date: $date\n    iso_country_code: $iso_country_code\n    last_seen_placekey: $last_seen_placekey\n  ) {\n    placekey\n    parent_placekey\n    location_name\n    street_address\n    city\n    region\n    postal_code\n    iso_country_code\n    safegraph_brand_ids\n    brands\n    date_range_start\n    date_range_end\n    raw_visit_counts\n    raw_visitor_counts\n    visits_by_day\n    visits_by_each_hour\n    poi_cbg\n    visitor_home_cbgs \n    visitor_home_aggregation \n    visitor_daytime_cbgs \n    visitor_country_of_origin \n    distance_from_home\n    median_dwell\n    bucketed_dwell_times \n    related_same_day_brand \n    related_same_week_brand\n    device_type\n  }\n}","variables":{"date":"2021-09-20","iso_country_code":"US","last_seen_placekey":""}}' --compressed

That works great. Now I can download the data.
For the final questions. Does it matter which API I use as the first one for "last_seen_placekey"? Or, it does not matter?
I understand there would be many requests. does it cause any problem from the server side? I just want to download responsibly.

For last_seen_placekey, I believe what you need to do is set that as empty for the very first query, which will return 500 rows, and then you should use the very last placekey returned to get another set of 500, etc. Does that answer your question?
And no limits on this bulk_weekly_patterns query type. We made this bulk endpoint specifically for users like you who wanted to download lots of data 🙂

from time import sleep
for i in placekeys:
   sgql_client.lookup(i)
   sleep(.33)
   sgql_client.save(i+".csv")

try it with caution


type existing prs in the job definition

What are you trying to accomplish?

See https://github.com/dependabot/dependabot-core/issues/9561

Replaces an Array of Hashes with an actual class! This prevents typos and makes Sorbet more useful.
Anything you want to highlight for special attention from reviewers?
One challenge here was we use a mini-version of Dependency. So I didn't want to reuse the Dependency class as the comparison is kind of special, so I made an inner-class Dependency under Pull Request. Is that confusing? Should it have a different name?
How will you know you've accomplished your goal?
This change should have no functional difference, so as long as the type checking and tests are passing, and no new errors popup after deployment we should be good.

Checklist

[x] I have run the complete test suite to ensure all tests and linters pass.
[x] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

I think I may have just fixed a bug with https://github.com/dependabot/dependabot-core/pull/10432/commits/3079ac2eb6d2a164ff4994338e6ab20b0be3941e. When checking to see if we already created a PR we should also consider PRs created by this very job.
The NuGet smoke tests used to be
updater | | created | AspNetCore.HealthChecks.Rabbitmq ( from 5.0.2 to 7.0.0 ), Microsoft.Extensions.Diagnostics.HealthChecks ( from 5.0.17... |
updater | | created | Microsoft.Extensions.Diagnostics.HealthChecks ( from 5.0.17 to 7.0.9 )                                                   |

but now it skips the second PR because it was already bumped in the first PR.


fix(helm): resolve relative chart paths

resolves #3168

I'm not sure if the updated docs should be part of this PR, but I found that the --repo install option is missing.
Furthermore, I'm find it challenging to write a test case for this fix. Maybe someone can guide me, as I'm new to the helm code and Go. All test cases in TestInstall don't use a server backend, as I understand the code. But if I reuse the test server from TestFetchCmd:

will the fake client really use it?
can I easily modify the test server to serve relative URL's?

Updating the docs is good.
For testing, I think I would suggest extracting that bit of logic you wrote into a function, and then just writing a simple test that asserts that the newly rewritten URL matches what you were expecting. Anything more is probably too elaborate.

Thanks for your comments. I turned the URL resolution logic into a function, as you suggested. Furthermore, I decided to apply it already in FindChartInRepoURL. That way, other commands, like fetch, can benefit from this fix as well.

Thanks!


Multithreading is causing tkinter to hang and crash

Restructure caused issues with tkinter. Need some way to synchronously access the user entered URL from the GUI.

The issue has been fixed using tkinter thread safe variables. Threads now only interface with the GUI through these variables.


SUCCESSFULLY ENHANCED THE FEEDBACK FORM AND THE FOOTER

Pull Request Format
SUCCESSFULLY ENHANCED THE FEEDBACK FORM AND THE FOOTER
Issue #421  : **ISSUE NAME:  ENHANCEMENT OF THE FEEDBACK FORM AT FOOTER
https://github.com/swaraj-das/Collect-your-GamingTools/issues/421
Type of PR

Add X in the box to specify the improvement type.
[ X ] Bug fix
[ X ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): ___________

Description
### Before the Changes:

The footer form had a basic design with standard input fields, minimal styling, and limited interactivity. The form lacked visual appeal and did not fully integrate with the footer's overall layout. There were no hover or focus effects, the button design was plain, and the form was not optimized for mobile devices. Additionally, the input fields had no icons, and the overall layout felt static, making the user experience less engaging.
After:
### After the Changes:

https://github.com/user-attachments/assets/073814c5-0212-49bb-aeb6-c7730d87c368

After the enhancements, the footer form now has a modern, interactive, and visually appealing design. The input fields and buttons feature smooth hover and focus effects, with icons that make the form more intuitive. The form container has a subtle gradient background and shadows, giving it a sleek, professional look. It is fully responsive, with optimized spacing and layout for both desktop and mobile devices. The real-time form validation and custom error messages improve usability, while the overall design integrates seamlessly with the footer, creating a cohesive and engaging user experience.
Checklist

Add X in the box to specify.
[X] I have performed a self-review of my code.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.

Additional Context
BY DOING SUCH ENHANCEMENT I GAVE THE EXACT GREAT SITE LEVEL INTERACTION AND EXPERIENCE TO THE FORM .
[hope you will merge the PR by respecting my  hardwork]
Thank you for reviewing my pull request!

SIR I HAD SUCCESSFULLY RESOLVE THE ISSUE NO: #421 BY DOING RESPECTIVE ENHANCEMENTS. SO I AM HUMBLY  REQUESTING YOU TO PLEASE REVIEW THE CHANGES AND MERGE THE PR. AND IF ANY ADDITIONS WANT GLADLY INFORM ME.


The service "mopa_barcode.barcode_service" has a dependency on a non-existent service "imagine".

Hello,
I have this error in mopa barcode;
Someone can you help

Hi,
yeah you need to install
https://github.com/avalanche123/Imagine to your project,
i will update the readme accordingly.


[Bug]: Value of useControlField is undefined on first render

Which packages are impacted?

[X] remix-validated-form
[ ] @remix-validated-form/with-zod
[ ] @remix-validated-form/with-yup
[ ] zod-form-data

What version of these packages are you using?

@remix-validated-form/with-zod": "^2.0.7"
"remix-validated-form": "^5.1.5"
"zod": "^3.22.4"
"zod-form-data": "^2.0.2"

Please provide a link to a minimal reproduction of the issue.
https://github.com/AlexanderKulia/use-control-field-example
Steps to Reproduce the Bug or Issue

Clone repo
Run yarn install
Run yarn dev
Open browser, open console
Refresh page, field is undefined before its values changes to "alex"

Expected behavior
I expected that the field's initial value is set to whatever is passed in defaultValues similar to useState<string>("alex"). Am I doing something wrong? Because with this behavior I have to change the type to string | undefined and handle undefined which is annoying in complicated dynamic forms
Screenshots or Videos
No response
Platform

OS: macOS, Linux
Browser: Chrome
Version: 121.0.6167.189

Additional context
No response

Have you tried using useEffect?
export const MyForm = () => {
  const [value, setValue] = useControlField(
    "myField",
    "myForm"
  );

  useEffect(() => {
    // Now we can update the value of the field
    // for whatever reason we need.
    setValue("Some value");
  });

  return (
    <ValidatedForm validator={myValidator} id="myForm">
      <MyInput
        name="myField"
        // This assumes your input component
        // has a `value` and `onChange` prop
        value={value}
        onChange={(e) => setValue(e.target.value)}
      />
    </ValidatedForm>
  );
};

Example in here:
https://www.remix-validated-form.io/reference/use-control-field

I consider it a bug as well. The workaround is to read the defaultValue from useField and set the form element value as value={value ?? defaultValue} where value would be read through useControlField.

This happens only when using useControlField outside the context of the form itself. This hook has the same limitations mentioned in the "Other Considerations" section on this page. Though admittedly it doesn't look like I documented that anywhere.
I think a potential API improvement we could make here is to allow passing a default value directly into the hook like you mentioned.
But this is more of an intentional (if unfortunate) trade-off of the current API, rather than a bug. If you think about it, in code that looks like this, it's impossible for the useControlField hook to know anything about the default values of the form.
const { defaultValues } = useLoaderData();

const [value, setValue] = useControlField("myField");

return (
  <ValidatedForm
    defaultValues={defaultValues}
    // ...etc
  />
)

There are 3 main ways to fix the issue your observing.
Manually provide a default
const [firstName = defaultValues.firstName, setFirstName] = useControlField("firstName");

Use setFormDefaults instead of the defaultValues prop
export const loader = async () => {
  return setFormDefaults(formId, {
    firstName: "alex",
    lastName: "k",
  });
};

Call useControlField inside the form
const ControlledInput = (props) => {
  const [value, setValue] = useControlField(props.name);
  return (
    <ValidatedInput
      value={value}
      onChange={e => setFirstName(e.target.value)}
      {...props}
    />
  );
}

RVF v6 has been released 🎉
This issue no longer exists in v6. If it's still a problem in that version, please feel free to open a new issue.
You can find the documentation here and the migration guide here.


Bugfix/typos

I was reading your material and decided to fix some typos, nothing fancy.
Please review the fixes.

Thanks @ahartikainen! I will take a look this week. (I think the travis fail is just because we let some things get out of date...)